cookieless tracking in walled garden

### Expected Behaviour

I can use alloy without cookies.
alloy can use a session mechanism that is provided by the caller.

### Actual Behaviour

alloy sets cookies to track the user

### Further Information

I'm not sure if this is the right place to ask for a feature, but please be kind and tell me where the right place is to request the feature when this one is wrong.
I want to explain the the request a little bit more. I'm working in the EU and the GDPR is strict in requesting a cookie banner when we set a non-technical-cookie. A tracking cookie is, as far as I know, a non-technical-cookie that needs a banner. I'm working in an environment where all users are logged in. There is no anonymous access. In such an environment we could use the session of the logged in user to identify him or his cohort (group he belongs to).
As far as I understand (https://experienceleague.adobe.com/docs/experience-platform/edge/web-sdk-faq.html) alloy use in all cases a cookie to track the user.

Some questions:
1. Do you support or have plans to support other identifying mechanisms?
2. Do you have a suggestion how to implement such a cookieless tracking mechanism?
3. I've seen that cookies are handled by a cookieJar.js (https://github.com/adobe/alloy/blob/main/src/utils/cookieJar.js) would it be a good idea to use this point to inject own logic?

I'm grateful for all support and ideas from your site.

Start by reviewing src/utils/cookieJar.js and the linked Alloy Web SDK FAQ to understand the current cookie-based identity behavior. Clarify the supported caller-provided session mechanism and define acceptance criteria for cookieless tracking before proposing an implementation; the issue is done only when the alternative behavior and its limitations are specified and tested.

Written by the indexing model from the issue text.