Add E2E tests for cloud guard, identity, faaas, logging, and migration

[shopewf]

Description

Includes E2E tests and mocking for:

• Cloud guard
• Identity
• FAaaS
• Logging
• Migration

Besides those tasks, this PR also addresses a few issues:

1. There was no way to override the config file location in servers. This is supposed to be a feature of the oci python sdk, but for some reason their logic only allows the OCI_CONFIG_FILE env var to override the default file location if the default file does not exist, when REALLY it should be falling back to the default location only if that env var is not present. Talked with @gebhardtr, he agrees this is an issue and approved this change. This was required because I realized my previous PR created the mock oci config, but it wasnt actually being consumed like I thought it was because the default path was being used instead. I will need to update unit tests for this change.
2. Identity client has a global endpoint that ignores HTTP/HTTPS proxy. This makes it so the normal method of supplying the proxy to the identity client to point it to our mock server doesnt work. I had to create a sitecustomize.py file that patches the identity client to pass in the service endpoint that points to our mock. Read more about sitecustomize.py files here: https://docs.python.org/3/library/site.html#module-sitecustomize
3. Data objects are sent over http with camelCase, but our data was snake_case (the pythonic way). I had to make the mock data camelCase to avoid some errors.

Type of change

Please delete options that are not relevant.

• E2E test updates

How Has This Been Tested?

Tested locally with behave features/<feature file>

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules