ci: add workflow to deploy Firebase rules

[staceybeard]

By submitting this merge request, I confirm the following:

• The merge request title follows the conventional commits convention (see Backend project's README.md)

Changes

Wrote a workflow to deploy Firebase rules via GitHub Actions. This is done automatically for dev, and can be run manually in any other available environment.

Also consolidated our Firebase rules files to only have one file for all environments.

Dependencies

• App: N/A

[staceybeard]

@mschoettle

For the pre-commit hooks, thanks for the reminder, I'll set those up 👍

I was able to run zizmor and address its findings, but actionlint fails for me with the following error:

did not run successfully while checking script at line:58,col:9: ...\pre-commit\repozpzbzmpq\golangenv-default\bin
\shellcheck.exe exited with status 1 but stdout was empty. stderr: "2025/04/07 14:13:58 environ invalid: empty key\n"

[mschoettle]

@mschoettle

For the pre-commit hooks, thanks for the reminder, I'll set those up 👍

I was able to run zizmor and address its findings, but actionlint fails for me with the following error:

did not run successfully while checking script at line:58,col:9: ...\pre-commit\repozpzbzmpq\golangenv-default\bin
\shellcheck.exe exited with status 1 but stdout was empty. stderr: "2025/04/07 14:13:58 environ invalid: empty key\n"

What I suggest we do is:

• let's add a pre-commit config to this repo
• we add a CI job that runs pre-commit

This gives us additional checks in the pipeline. And we leave it optional to install the hooks locally.

[mschoettle]

Run firebase deploy --only database

Error: Invalid project id: $VAR_PROJECT_ID.
Note: Project id must be all lowercase.
Error: Process completed with exit code 1.

Can you DM me the contents of the secret? In GitHub it is not possible to read secrets in the settings once they are set.

[staceybeard]

@mschoettle The <ENV>_FIREBASE_PROJECT_ID values aren't secrets, they're on the variables tab, so you should be able to view them.