Implement a cookieless tracking option

So we probably don't need it for now?
For the time being, anyone who needs it, can simply adjust the "init_config_json" to use a different persistence setting. I am even unsure, if we should provide a setting for this at all. The cookies + klaro integration should be enough for 70% of all cases and the rest can simply change the persistence in "init_config_json".

Re #4: Maybe we should simply document this below the snippet and link to the posthog documentation? And maybe inform users about available integrations in Klaro and COOKiES? (That don't yet exist, right?)

>Re #4: Maybe we should simply document this below the snippet and link to the posthog documentation? And maybe inform users about available integrations in Klaro and COOKiES? (That don't yet exist, right?).

You are saying we should document this below the json_init field? Unsure about this. Unsure about this. Maybe we should link to the help page below the field and add the information to the help page?

Give it a try in a MR and we can have a look.

Done, please review!

Just a note. I am not generally a big fan of one README per submodule, so I put all the information inside the main modules README, we could eventually also move the js information down into its own section.

Nice, just add the https://posthog.com/docs/configure/initialization-configuration link to section in the README also for details. Then this is fine for me!

Done!

Merging.

Automatically closed - issue fixed for 2 weeks with no activity.