Update workflows to use actions that don't need organization secrets

[jdbaldry]

Each repository can only have 100 organization secrets and there are now more than 100 in our organization which causes inconsistent behavior.

Some repositories don't have the secrets they need assigned.

These composite actions use secrets stored in Vault that are available to all repositories.

• publish-technical-documentation-next.yml has been tested with https://github.com/grafana/writers-toolkit/blob/main/.github/workflows/publish-technical-documentation.yml.

Special notes for your reviewer:

There is some copy-paste involved in the creation of these workflows. Please check:

For publish-technical-documentation-next.yml:

• [x] The on.push branches and paths filters are correct for your repository.
• [ ] The jobs.sync.if repository matches your repository.
• [ ] The jobs.sync.steps[1].with.website_directory matches the directory you publish to in the website repository.

[knylander-grafana]

The directories all look okay to me.

The drone build fails on all PRs because of the spell check issue.