fix(plausible): domain update

[theJohnnyMe]

Describe pull-request
Updating Plausible domain for develop branch

Solving issue
Fixes: CDEP-2890

How to test

1. Check if the domain in code changes is updated to new one (tds-storybook.tegel.scania.com)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[aws-amplify-eu-north-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-380.d3fazya28914g3.amplifyapp.com

[alexandereneroth]

I suggest two PRs as you did, but with the same branch, otherwise git will still consider them out of sync, even if they contain the same changes.
We also might have to remove the branch auto deletion on merge.

[theJohnnyMe]

I suggest two PRs as you did, but with the same branch, otherwise git will still consider them out of sync, even if they contain the same changes. We also might have to remove the branch auto deletion on merge.

Good that you commented. I would propose this:

1. Close this PR
2. Merge changes to the main branch so we get tracking in the place (in other PR)
3. Rebase develop with main so develop has whatever main has + its new changes
4. Live happily ever after

@alexandereneroth - what do you think of this approach?
I think I can do it as I can bypass GitHub rules.