Fix GitHub Actions workflow for forked repositories

[printfer]

Currently, the GitHub Actions workflow does not run correctly on forked repositories. This is a minor issue, but it would be great to fix it alongside #21.

The chromatic.yml workflow fails due to the lack of a secret token. To fix this issue, we need to check if the secret token exists before executing the workflow. Here's an example:

  env:
    HAS_CHROMATIC_PROJECT_TOKEN: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
  steps:
    - if: ${{ env.HAS_CHROMATIC_PROJECT_TOKEN }}
    ...

You can find more details on how other people have resolved this issue at github/docs#6861.

For the release-please.yml workflow, I suspect that the default setting prevents it from running on forked repositories, but I'm not entirely sure. To prevent the workflow from running in a forked repository, we can add a check like this:

if: "! github.event.pull_request.head.repo.fork " 

You can find more details about this issue at https://github.com/orgs/community/discussions/25217#discussioncomment-3246904.

By implementing these fixes, we can ensure that the GitHub Actions workflow runs correctly on forked repositories. This will improve the overall usability and accessibility of our repository.

[edjonesdev]

Fixed with #24