CI shouldn't fail when secrets are missing in forks

[jsoref]

Fixes #issue_number

Problem

CI fails miserably when run in forks.

Solution

This adds an extra tiny job to the ci workflow that checks for the secrets that appear to be essential to the build and only sets an output when they're present.

The stages that need those secrets are then conditioned on the presence of the secrets.

Notes

I've also fixed the indentation of the ci.yml file as the one-space indentation makes it really hard to follow the file.

Checklist

• Unit test all changes
• Update README.md if applicable
• Add [WIP] to the pull request title if it's work in progress
• Squash commits that aren't meaningful changes
  • Squashing changes eagerly makes it really hard to review the changes. I'm happy to squash once people are ok w/ the changes themselves.
• Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

[juliano]

@guizmaii after your changes regarding the ci/release, is this one still useful?

[guizmaii]

@jsoref Can you please rebase on the main branch, please?

[jsoref]

Hmm, by main, I presume you mean master -- there's a main, but it's really behind (quite confusingly)...

[guizmaii]

LGTM

[juliano]

Thank you for the contribution!