🐛 Submitting Governance Action with IPFS Metadata URL Fails Due to Unsupported URL Scheme

### Area

Proposal Pillar

### Domain

gov.tools

### Which wallet were you using?

Eternl 2

### Context

When promoting a proposal from the **Proposal Discussion Forum** (off-chain) to an actual on-chain **Governance Action**, users have the option to store the metadata on **IPFS** and provide the IPFS URL in the final submission step. This is meant to validate whether the metadata file generates the same hash as what is expected by the governance action transaction.

This feature was **previously supported** as confirmed in [GitHub Issue #3851](https://github.com/IntersectMBO/govtool/issues/3851). However, the functionality is now broken — entering an `ipfs://` link results in a browser error.

### Steps to reproduce

1. Go to the **Proposal Discussion Forum**.
2. Create a new proposal or use an existing one.
3. Proceed to submit the proposal as an **on-chain governance action**.
4. On the final step, choose to **store the metadata on IPFS** and paste an `ipfs://` link into the field.
5. Observe the error in browser developer tools console.

### Actual behavior

- The interface fails to validate the IPFS URL.
- Console logs the following error:

`Fetch API cannot load ipfs://. URL scheme "ipfs" is not supported.`


- Fetch API cannot load ipfs://. URL scheme "ipfs" is not supported.

### Expected behavior

- `ipfs://` URLs should be handled properly by routing through an HTTP-compatible IPFS gateway (e.g., `https://ipfs.io/ipfs/`).
- The metadata hash should be calculated and validated as before.
- No Fetch API errors should occur.