Documentation: Add contributing note for disabling actions in forks

[johnhunter]

What I did

• Added a note about disabling actions when forking the repo. Most forks will be used to dev locally on the project and raise PRs so the actions don't make sense and will just cause errors.
• Added an issues section to help contributors solve known issues.
• Fixed a broken link to the contributing guide

How to test

Documentation only.
If required you can confirm contributing guide link does not 404.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[johnhunter]

Ok, failing on Danger JS 😳 - I made the docs changes in the GH site. I'll pull down the PR locally and have a look in a bit.

[johnhunter]

Am getting errors running yarn start locally so moving this PR to draft until resolved.

[johnhunter]

Ok, the failing CI on this PR is unrelated to my local issues so setting back to review.

[kylegach]

Thanks for these improvements, @johnhunter!

I left some suggested further improvements for you to integrate, then we can merge.

[kylegach]

Nicely done! Thanks again, @johnhunter.