ci: add alteration scripts compatibility test jobs

[simeng-li]

Summary

To address the issue of production errors caused by incompatible database alterations, we're introducing a new CI job dedicated to ensuring the compatibility of alteration scripts with our production code. This job aims to prevent altered data from breaking our production systems when the production DB has been altered but the new release code is launched to staging only.

1. returns directly if no alteration script changes are detected
2. pull the base branch codebase and init logto
3. run the db alteration from the current branch
4. run the integration tests on the base branch logto server

This PR refactors the integration test, all the shared integration steps are extracted to the latest created custom GitHub actions:

• logto-io/actions-package-logto-artifact
• logto-io/actions-run-db-alteartion-steps
• logto-io/actions-run-logto-integration-tests

PLEASE review the above actions as well.

Testing

Happy test

test based on the PR #4616.

• init the db using the master
• run the alteration script from PR feat(schemas): init organization tables #4616.
• run the integration tests based on master code.

Failing test

Simulate the PR #4582

• old head branch-based integration test:

• new base branch-based integration test with db alteration:

Checklist

• .changeset
• unit tests
• integration tests
• docs

OR

• This PR is not applicable for the checklist

[linear]

LOG-7144 CI: Add integration for staging period

目前 staging 时的测试还未被覆盖。
staging 时，db 是最新（alteration 之后）的状态，但是代码还是旧的版本。
这个时候 db 应该兼容旧的代码，需要新增 旧代码 + 新 db 的场景的场景的测试。

[github-actions]

COMPARE TO master

Total Size Diff 📉 -61 Bytes

Diff by File

Name	Diff
.github/workflows/alteration-compatibility-integration-test.yml	📉 -2.21 KB
.github/workflows/integration-test.yml	📉 -2.26 KB