feat(telemetryrouter): Onboarding TelemetryRouter

[ozanichkovsky]

Description

Telemetry Router resources and datasource

Checklist

• Issue was linked above
• Code format was applied: make fmt
• Examples were added / adjusted (see examples/ directory)
• Docs are up-to-date: make generate-docs (will be checked by CI)
• Unit tests got implemented or updated
• Acceptance tests got implemented or updated (see e.g. here)
• Unit tests are passing: make test (will be checked by CI)
• No linter issues: make lint (will be checked by CI)

[github-actions]

This PR was marked as stale after 7 days of inactivity and will be closed after another 7 days of further inactivity. If this PR should be kept open, just add a comment, remove the stale label or push new commits to it.

[GokceGK]

You should not use hard coded token like that. This wont work.

[ozanichkovsky]

Destination represents an external destination logs are sent to. So it is a value, which a service user provides, not something that is generated by us.

[ozanichkovsky]

The only possibility I probably see is to use another instance as a destination with a token created for that instance. Should it be done that way?

[GokceGK]

What is meant by the external destination ? Where is this token generated and provided? Do we have another resource dependency? What is the lifetime of this token?
In worst case scenario, the token must be given via ENV variable. Cause we want to run our acc tests without changing the code base with new values.

[ozanichkovsky]

Telemetry Router allows logs to be sent to external destination added by a customer. It is just a minimal token from https://www.jwt.io. But we've recently added a health check on Destination creation in order to be sure that logs can be sent to it. That means I'll have to add another Telemetry Router instance with a token created for it and use it as a target for the Destination.