Docs: Rename/move 'introduction' to 'key concepts' and fix broken links

[josmperez]

Complete 2nd stage of the plugin-tools site reorganization project. Move/rename site, fix broken links.

Fixes: https://github.com/grafana/plugin-tools/issues/925

[github-actions[bot]]

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

[josmperez]

Eliminating no-changelog label because there were fixes of broken links in the packages.

[josmperez]

Changing to draft to allow for fixing of failing check and additional testing.

[josmperez]

Per Slack conversation, it's okay to ignore failing test. Moving from draft to review status.

[CLAassistant]

All committers have signed the CLA.

[josmperez]

@tolzhabayev @jackw @academo - Hi, I'm having difficulty testing some of the redirects. They look to be properly formed in the docusaurus/website/docusaurus.config.base.js file; also, when the old URL is entered into the browser's address bar, the links go to a page with the correct content. However, the page that is displayed appears at the wrong URL when testing on the dev server.

For example,

• the new page at https://grafana-dev.com/developers/plugin-tools/key-concepts/backend-plugins/grafana-plugin-sdk-for-go is redirected from the current page at https://grafana.com/developers/plugin-tools/introduction/grafana-plugin-sdk-for-go.
• However, when you type in https://grafana-dev.com/developers/plugin-tools/introduction/grafana-plugin-sdk-for-go
• you expect to get https://grafana-dev.com/developers/plugin-tools/key-concepts/backend-plugins/grafana-plugin-sdk-for-go
• but you get instead https://grafana-dev.com/developers/plugin-tools/introduction/grafana-plugin-sdk-for-go
• and the left navigation bar now contains the old Introduction section but not the new Key Concepts section
• even though the Introduction section has been deleted from the josmperez/key branch

I guess this is some sort of caching issue, however I'm not sure and I would like to resolve this problem so the redirects can be properly tested before the PR is published.

Thoughts on what is going wrong and how to fix it?

[tolzhabayev]

@josmperez there were still some wrong links in this branch that's why the build did not work properly, and that's why it never actually got deployed to dev stage.

adding to that - it was quite outdated so the errors did not surface locally but only when running in CI.

We have made the fixes and pushed them directly in this branch and deployed to dev - so please pull your changes and now you should be able to see the redirects working.

[josmperez]

@josmperez there were still some wrong links in this branch that's why the build did not work properly, and that's why it never actually got deployed to dev stage.

adding to that - it was quite outdated so the errors did not surface locally but only when running in CI.

We have made the fixes and pushed them directly in this branch and deployed to dev - so please pull your changes and now you should be able to see the redirects working.

Excellent, thank you all for the troubleshooting assistance. I finished testing the files that couldn't be verified appropriately, and then fixed a few other errors as well.