Add the example dashboard to the test site

[Rockerby]

In line with #3, this adds in the example dashboard from the core templates.

Didn't need to do anything fancy, simply followed the instructions from the docs and voila, a new dashboard in the test site! I did have to fix some issues with the template; update hey-api/client-fetch version and a type issue in the dashboard.element (didn't have time so hacked it with // @ts-nocheck). I'll take a look and sort that in the main CMS if someone hasn't beaten me to it.

I've added in the generated files, so maybe we want to add the app_plugins to the gitignore and figure out how to build in the pipelines?

[Rockerby]

As per the instruction in the issue, I updated this to point at the main branch - which resulted in a conflict. It's a comment in a yml file which I'll leave you to deal with 😊

Edit: for clarity I forked from your develop branch

[nul800sebastiaan]

I think the src/OpenSourceTest.MyExtension/wwwroot/App_Plugins/OpenSourceTestMyExtension/ folder should probably be in the .gitignore as that is build output. GitHub actions should build those before shipping it off to Cloud.

[jemayn]

It might make sense to set up an extension as a bundle early on - atleast for the community site - and figure out the github action and deployment and gitignore portions of it.

That way contributors can just add new extensions to the bundle and all those other considerations should not matter as long as they stick to the predetermined folder structure 🤔

[LottePitcher]

Thanks @Rockerby and @jemayn for looking at this

Shall be trying it later today! 🤞

[nul800sebastiaan]

Thanks @Rockerby ! We've done some rework with the generated files and this is now merged.