fix: make samesite and domain attributes configurable for frontend sdk cookie

[lfleischmann]

Description

• The SameSite attribute is not set for cookies set by the SDK.
• The cookie will only be sent for requests to the exact same domain but not to subdomains.

Fixes #1245
Fixes #699

Implementation

This PR makes both the SameSite and the Domain attribute configurable in the frontend-sdk via options when instantiating the main client instance and via the elements options when register-ing components.

How to test

1. Modify /etc/hosts file, e.g. add

127.0.0.1 myapp.local
127.0.0.1 api.myapp.local

2. Modify frontend/examples/express files: :
   • In server.js change corsOptions.origin from localhost to myapp.local :

      const corsOptions = {
      	origin: "http://myapp.local:8888",
      	...,
      };
     
     

   • In .env, change HANKO_API_URL to the API URL of a Hanko Cloud instance.
3. Select one of the example applications, e.g. React. In that case, modify frontend/examples/react files:
   • In .env, change REACT_APP_HANKO_API to the API URL of a Hanko Cloud instance and REACT_APP_TODO_API to http://api.myapp.local:8002.
4. Set the correct API URL in your Hanko Cloud project, i.e. http://myapp.local:8888.
5. Run npm run build in the frontend directory.
6. Run npm run start for both the frontend/examples/express and the frontend/examples/react app.
7. Modify options passed to register calls in frontend/examples/react (i.e. in HankoAuth/HankoProfile).

Todos/Issues/Questions

• Should the SameSite attribute even be configurable, or should we just set it to a default?