🐛 Offer a raw JSON view of governance metadata to conform to CIP-100 best practices

### Area

Voting Pillar

### Domain

gov.tools

### Which wallet were you using?

_No response_

### Context

- GovTool should follow the best practices defined via the community governance metadata standard CIP-100
- [CIP-100 Best Practices](https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#best-practices) states that:
> You SHOULD gracefully degrade to a simple raw content view if the metadata is malformed in some way, or not understood.

This means that when metadata is flagged as erroneous and it cannot be nicely rendered, GovTool should offer the user a raw JSON view of the metadata.
GovTool does not do this at the moment for either governance action metadata or DRep metadata.

### Steps to reproduce

see example action with extra metadata field https://preview.gov.tools/governance_actions/b51ce01c42be5a1b1fbbe665ccc0f71a4c06754153ce74616f44dcd5ef8b5d05#0

when adding an extra field in metadata
https://github.com/Ryun1/metadata/blob/main/extra-field.jsonld#L55

### Actual behavior

No way to view raw JSON metadata in erroneous or happy path

### Expected behavior

I believe there is an approach that would work simply nicely
- we add a new tab on the governance action details page to view the raw metadata, for erroneous actions and non-erroneous actions
- we add a new tab on the DRep details page to view the raw metadata, for erroneous metadata and non-erroneous metadata

This has the added benefit of allowing the user to discover new data fields that have been used and submitted.

on governance actions


on DRep metadata