Add Correlation Identifiers to Requests Originating from the User Interface

[bencap]

As an extension of VariantEffect/mavedb-api#80, we should add functionality to the front-end that sends an X-Correlation-ID header with each outgoing request. These correlation identifiers (c-ids) should be generated for distinct interactions a user undertakes (generally, they should change with each un-correlated user action).

In practice, this might mean different things for different resources. As an example, a user might navigate to the score set creation wizard. All requests made while the user is on the score set wizard page should be correlated. However, once the user submits the new score set and a new GET request is issued for the modified score set, we should execute that request with a new c-id.

We can probably implement this as an extension of the compositions module, with a Pinia store tracking the correlation identifier and code set up to modify the correlation identifier as necessary. The managed c-id should be injected into all outgoing requests to our backend.