Jvd/orgs

[jduss4]

Changes proposed in this pull request:

Fulfills step 2 of #102

• adds example-fied API responses for /v3 org endpoints (org list, org, org users)
• moves cloudfoundry tests to __tests__
• takes existing getCFApps function and makes reusable for listing apps and orgs
• adds useUnknownInCatchVariables for tsconfig to get around using any for error (see docs)

This is an extremely rough implementation of grabbing information about orgs the user has access to. It lacks error handling and jumps straight to the .resources portion of an API response. Now that our users can successfully receive org information from the CF API, we will want to invest time thinking about additional response data we want to use, like pagination / count, understand CF error messages beyond just the returning http code, etc. This will require refactoring in the cloudfoundry.ts file and possibly api.js.
The UI is left untested as it is expected to change drastically in the near future.

Things to check

• For any logging statements, is there any chance that they could be logging sensitive data?
• Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.
• Have you updated or added relevant documentation (README, ADRs, explainers, etc)?

Security considerations

The API requests are available to unauthenticated users, although without a correct token for the CF API they will receive a 401 response.
In the test mock files, I have replaced all GUIDs, usernames, org names, etc to make for a generic but realistic API response.

[echappen]

looks great, thanks!