Fix hardcoded schema in Postgres reschedule query

[thomasjiangcy]

Summary

• replace the remaining hardcoded "openworkflow"."workflow_runs" update target in BackendPostgres.rescheduleWorkflowRunAfterFailedStepAttempt with the configured schema table helper
• add a regression test that exercises rescheduleWorkflowRunAfterFailedStepAttempt with a custom schema to prevent regressions

Testing

• npm run ci

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

This PR removes the last hardcoded "openworkflow"."workflow_runs" reference in the Postgres backend reschedule path, ensuring schema customization is respected, and adds a regression test to prevent this from breaking again.

Changes:

• Update BackendPostgres.rescheduleWorkflowRunAfterFailedStepAttempt to use this.workflowRunsTable() instead of a hardcoded schema-qualified table name.
• Add a Vitest regression test that verifies rescheduling updates the workflow run row in a custom schema.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/openworkflow/postgres/backend.ts	Uses the schema-aware table helper in the reschedule UPDATE query to support custom schemas.
packages/openworkflow/postgres/backend.test.ts	Adds a regression test validating rescheduling works when schema is customized.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jamescmartinez]

great find, thank you @thomasjiangcy for finding this and for the PR!

this was my fault - I had #294 going in parallel to your PR #293, so the query didn't support your new configurable schema work.

[thomasjiangcy]

thanks for letting me know!

[jamescmartinez]

@thomasjiangcy released in 0.7.1