chore(analytics): include project and user metadata when running commands with noProject

[mkhq]

What this PR does / why we need it:

Optionally includes project and user metadata when running a command with noProject = true. Internally, we instantiate a DummyGarden instance which is not having project or user metadata available. In addition, we only set the enterpriseDomain field if its defined in the project config.

To achieve this there are a couple of notable changes:

• The global store is extended with a cloud user profile including userId and organizationName for each associated domain
• A profile request is made when logging in to a cloud domain to ensure the existence of the user and to store the metadata in the global store upon login
• When analytics is called with a DummyGarden-instance, it tries to fetch the project name and cloud domain from the config + does a lookup of the cloud user profile
• Mocha tests are called with an additional flag to handle nock and fetch compatibility (Node 18+: make nock work native fetch nock/nock#2397)
• Version checks are disabled in tests unless explicitly part of the tests. This was always the case for circle CI which is why the nocked version check service tests always failed.
• Extends the pendingRequests for identify analytics events to make sending them more robust
• Only sets the cloudDomain when logged in
• Only sets the enterpriseDomain and enterpriseProjectId when defined in the project config

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

• Auth token validity check is best effort, opted for that approach now instead of pulling in a JWT library

[eysi09]

Great stuff!

I had a couple of comments but otherwise looks good.

[eysi09]

This is kind of an awkward name. Should we skip this for non-enterprise?

[eysi09]

Don't we already do this in the in line 92?

[eysi09]

Can we extract this to a separate function and update the control flow so that it doesn't have all these nested if statements?

We can instead return early with something like:

if (!projectConfig) {
  return
}

// proceed...