Have multiple INGESTION_KEYs

[maelp]

I guess the INGESTION_KEY is not really a secret because it leaks in the frontend.

Perhaps we could have multiple INGESTION_KEYs, with eg different rate-limits, etc

so our own backend could securely use an INGESTION_KEY with a high rate-limiting, and the browsers would be more limited, in case the key leaks?

[teeohhem]

Thank you. We do have a ticket in our backlog to implement support for multiple ingestion keys, etc.