Setup repo for community maintenance

[Sidnioulz]

• Add CI/CD workflows from e.g. https://github.com/storybook-community/storybook-source-link/tree/main/.github
• Align script names in package.json to match CI/CD workflows and other repos
• Review addon metadata
  • tags
  • icon
• Make sure the version in package.json matches the current release
• Edit README to include thank you note for original addon author

📦 Published PR as canary version: 9.0.2--canary.15.3e3d0e9.0

✨ Test out this PR locally via:

npm install @storybook/addon-queryparams@9.0.2--canary.15.3e3d0e9.0
# or 
yarn add @storybook/addon-queryparams@9.0.2--canary.15.3e3d0e9.0

To fix this issue, add the permissions key to the workflow file to explicitly set the minimum permissions required. Since neither the lint nor the build job needs to perform write operations (such as creating issues, pushing code, etc.), contents: read is a sufficient and secure default. Add this at the workflow root, after the name and before on, so it applies to all jobs. No other code or configuration changes are needed in this case.

---

To fix this problem, set an explicit permissions block restricting what the GitHub Actions jobs can do via the GITHUB_TOKEN. Since the workflow only runs linting and build steps (with no deployment, PR, or issue manipulation), the minimal required permission is contents: read. We should add the following at the top level, just below the workflow name, so it applies to all jobs. No change to functionality will result from this alteration.

• File/region to change: .github/workflows/continuous-integration.yml, directly below the name: CI (after line 1).
• What is needed:
  Add a permissions section:

  permissions:
    contents: read

  No further imports, method, or definition changes are needed.

---