feat: Cache identity responses

[rmi22186]

Instructions

1. PR target branch should be against development
2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

We want to cache our identity responses to limit superfluous identity calls. This applies to login and identify for now. In this PR, I leveraged the vault in order to create a new idCache.

The keys for the idCache are a concatenation of the identities being passed to it along with the das. An example value is as follows:

{
    mpid: 'foo',
    responseText: // cached response from the XHR request
    expirationTimestamp: // number - the date being 1 day added to the time the identity call was made
}

When an identify or login call is attempted, the idCache is checked. If it is valid, we simply return the cached information, and do not make an identity call. If the key does not exist, or it has expired, then we fire another identity call, and cache that one.

Testing Plan

• Was this tested locally? If not, explain why.
  Integration tests. Unit tests.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://go.mparticle.com/work/SQDSDKS-5976

[sonarqubecloud]

Quality Gate failed

Failed conditions

6.9% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud