feat(db): make PostgreSQL sequences resync more robust

[joshtrichards]

• Resolves: [Bug]: Conversion of MariaDB to Postgres17 fails on oc_storages_numeric_id_seq sequence #56128

Summary

We fail silently and/or break part way through conversions in some cases in unusual ways.

Why? The current resync code needs additional error checking.

Additionally we also retrieve things in some semi-brittle ways.

This PR:

• makes all known failure scenarios explicitly throw (multiple sequence owners, no sequence owners, insufficient privileges)
• introduces more robust ways of retrieving sequence owners and setting sequence values (with fall back behavior)
• hardens binding / identifier handling to make a bit more resilient

Tried to keep business logic manageable/readable by introducing changes via smaller/dedicated helpers.

BREAKING CHANGE: resynchronizeDatabaseSequences now fails fast for sequences with no owner or multiple owners and requires UPDATE privilege (or ownership) to set sequences; callers that relied on the previous silent (or unpredictable) behavior should be aware these invalid states are now detected.

It'd be nice to add some unit / integration / e2e tests for the DB converter. AFAIK there aren't any currently.

TODO

• Incorporate fix: Set correct sequences converting MySQL to PostgreSQL #56575 into the fall back (shouldn't impact the more authoritative/preferred code path but still relevant with the fall back in place)
• See about adding some basic unit tests
• See about adding an E2E test for occ covert

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)