docs(runbooks): add API, queue/jobs, and payments operational guides

[jimmypalelil]

Issue:

• [Ops] Document runbooks for common issues in the strr-api service #1442

Description of changes:

• Add runbook documentation for strr-api operations, including health endpoints, configuration pitfalls, auth/role handling, common startup failures, and production troubleshooting guidance.
• Add runbook documentation for queue services and Cloud Run jobs, covering strr-pay, strr-email, permit validation listeners, trigger flows, logs, retries, and diagnostics.
• Add a payments runbook describing end-to-end payment flow, API touchpoints, status transitions, reconciliation pointers, and triage steps for failed/missing updates.
• Update ignore rules for examiner web generated artifacts.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the BC Registry and Digital Services BSD 3-Clause License

[bcregistry-sre]

Temporary Url for review: https://strr-examiner-dev--pr-1479-nof6it87.web.app

[thorwolpert]

You could also create these as Jupyter notebooks, the queries can be run in the page.
Examples are here:
https://github.com/bcgov-c/hous-str/tree/main/notebooks

[jimmypalelil]

You could also create these as Jupyter notebooks, the queries can be run in the page. Examples are here: https://github.com/bcgov-c/hous-str/tree/main/notebooks

@thorwolpert I thought about adding notebooks in this repo itself but thought it might be overkill for the scope of the task. also is there a reason why those notebooks are in a different secure org (bcgov-c) repo hous-str? We could have just added them in this repo right since its str related?

---

On another note I am thinking of putting up the GCP log queries with gcloud cli using this extension:

%load_ext pshnb

%%bash
gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=strr-api-dev" --format="table(timestamp, textPayload)" --limit=10 --freshness=1h

But it can be planned for a later time I suppose.

[thorwolpert]

Yep, although we have a different audience in the "confidential" org, so if they happen to save things they shouldn't by accident it's not the same blast-radius as it is in the public repo

[dimak1]

LGTM!

[bcregistry-sre]

Temporary Url for review: https://strr-examiner-dev--pr-1479-nof6it87.web.app

[Jacky-Pham]

Look good to me!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[bcregistry-sre]

Temporary Url for review: https://strr-examiner-dev--pr-1479-nof6it87.web.app