💡 Adapt GovTool for Intra-Era Hard Fork (Protocol Version 10 → 11 Upgrade)

### Area

Other

### Is there new design needed?

No

### What?

Prepare and update GovTool to remain fully functional during and after the **upcoming intra-era hard fork**, which will upgrade Cardano’s **major protocol version from 10 to 11**.
This might require adjustments in both backend and frontend components to ensure that governance-related data (proposals, voting, outcomes, and metadata) remains consistent and compatible with the anticipated updates that will be introduced in protocol version 11.

### Why?

An **intra-era hard fork** occurs when the protocol version increases (e.g., 10 → 11) without transitioning between major eras (Voltaire → Voltaire).

Without adaptation, GovTool could experience:
- Governance Actions not being displayed or validated correctly.
- Failed vote submissions due to mismatched protocol parameters.
- Incorrect metadata or epoch-based logic errors.

### How?

1. **Backend Adjustments**
2. **Node Integration**
3. **Frontend & UI**
4. **Testing and Validation**
5. **Fallback Plan**

### (Optional) User Story with acceptance criteria

**As a GovTool maintainer**,
I want GovTool to seamlessly support the protocol version 11 upgrade,
so that users can continue to create, view, and vote on Governance Actions without interruption or errors.

- [ ] GovTool backend and frontend run without errors post-upgrade to protocol v11.
- [ ] All Governance Action types remain creatable, viewable, and votable.
- [ ] DB queries correctly adapt to any updated db-sync schema.
- [ ] No data loss or mismatch between epochs before and after upgrade.
- [ ] Successfully tested in Preview and Preprod before Mainnet rollout.