feat(scorecard)!: add database and schedulers

[dzemanov]

Hey, I just made a Pull Request!

Adds database.
Adds schedulers.

Fixes

https://issues.redhat.com/browse/RHIDP-8717

How to test

1. Use sqllite database

backend:
  database:
    client: better-sqlite3
    connection:
      directory: './db'

Creates db directory under scorecard/packages
Or:

backend:
  database:
    client: better-sqlite3
    connection: ':memory:'

2. Use Postgres db

backend:
  database:
    client: pg
    connection:
      host: localhost
      port: 5432
      user: ${POSTGRES_USER}
      password:${POSTGRES_PASSWORD}

For testing purposes, you can update schedule to fetch metrics more often:

scorecard:
  dataRetentionDays: 1
  plugins:
    jira:
      open_issues:
        schedule:
          frequency: { minutes: 2 }
          timeout: { minutes: 15 }
          initialDelay: { seconds: 3 }
    github:
      open_prs:
        schedule:
          frequency: { minutes: 2 }
          timeout: { minutes: 15 }
          initialDelay: { seconds: 3 }

You should see in logs:

2025-10-03T19:46:36.590Z scorecard info Task worker starting: github.open_prs, {"version":2,"cadence":"PT2M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} task="github.open_prs"
2025-10-03T19:46:36.591Z scorecard info Task worker starting: jira.open_issues, {"version":2,"cadence":"PT2M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} task="jira.open_issues"
2025-10-03T19:46:36.591Z scorecard info Scheduled 2/2 metric providers 

2025-10-03T19:46:39.595Z scorecard info Refreshing metrics for github.open_prs class="MetricProvidersScheduler" taskId="github.open_prs:refresh" taskInstanceId="8ba58bad-08e8-4005-8b7f-314fde6e3bb9"
2025-10-03T19:46:39.596Z scorecard info Refreshing metrics for jira.open_issues class="MetricProvidersScheduler" taskId="jira.open_issues:refresh" taskInstanceId="026e7e65-085a-4592-956d-df554f697b4c"

2025-10-03T19:46:40.543Z scorecard info Completed metric refresh for jira.open_issues: processed 2 entities class="MetricProvidersScheduler" taskId="jira.open_issues:refresh" taskInstanceId="026e7e65-085a-4592-956d-df554f697b4c"
2025-10-03T19:46:40.758Z scorecard info Completed metric refresh for github.open_prs: processed 3 entities class="MetricProvidersScheduler" taskId="github.open_prs:refresh" taskInstanceId="8ba58bad-08e8-4005-8b7f-314fde6e3bb9"

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or Updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)

[rhdh-gh-app]

Important

This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior.

Unexpected Changesets

The following changeset(s) reference packages that have not been changed in this PR:

• /home/runner/work/rhdh-plugins/rhdh-plugins/workspaces/scorecard/.changeset/olive-months-cross.md: @red-hat-developer-hub/backstage-plugin-scorecard

Note that only changes that affect the published package require changesets, for example changes to tests and storybook stories do not require changesets.

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-github	workspaces/scorecard/plugins/scorecard-backend-module-github	major	v1.0.0
@red-hat-developer-hub/backstage-plugin-scorecard-backend-module-jira	workspaces/scorecard/plugins/scorecard-backend-module-jira	major	v1.0.1
@red-hat-developer-hub/backstage-plugin-scorecard-backend	workspaces/scorecard/plugins/scorecard-backend	major	v1.0.0
@red-hat-developer-hub/backstage-plugin-scorecard-node	workspaces/scorecard/plugins/scorecard-node	major	v1.0.0

[dzemanov]

Would maybe prefix it with scorecard: just to be sure it doesn't intersect anything.

[dzemanov]

I would add breaking here since we are now requiring getCatalogFilter
**BREAKING**: ...

• Add information about what is breaking - getCatalogFilter

[gashcrumb]

Do we need this line here, as it's already on line 61? Or is there another spot where this function is called from that could expect to receive the exception thrown on the next line?

[imykhno]

Thank you for your comment, this logger is not necessary I will remove it

[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

[dzemanov]

Retested again and tested the new deletion functionality, works great, thank you @imykhno.
I updated the changeset to major due this being breaking changes.