[FEATURE] - query the node for the max protocol version supported.

## What

As an SPO or DREP or CC, after updating my node to the version that supports a specific hardfork, I want to query the node for the maximum protocol version it supports before casting my vote, so that I can confirm it supports the protocol version required by the hardfork.

## Why

What if it doesn't? :scream: How do I know?

## Acceptance Criteria

When I send a query to the node requesting the maximum protocol version it supports,
then:
- The node returns the maximum protocol version it currently supports
- The response should be received within a reasonable timeframe.
- The response is clear about Major and Minor components of the protocol version.

## Personas

- [x ] SPOs
- [x] DReps
- [x] CC members
- [ ] dApp Devs
- [ ] Exchanges
- [ ] Wallets
- [ ] 3rd party tools
- [x] ADA holders

## Definition of Done (DoD)

- [ ] [Acceptance Criteria + User Stories & DoD](https://input-output.atlassian.net/wiki/spaces/QA/pages/3584229468/Acceptance+Criteria+DoD) created and singed-off (by PO, dev & test owners)
- [ ] Builds successfully on CI
- [ ] Code & Test review (as per Acceptance Criteria)
- [ ] There is documentation and/or examples for the new functionality (usage/response)
- [ ] Log/record changes on **Vnext** (or similar depending on what we adopt)
- [ ] Ticket number(s) included in PR description
- [ ] All Acceptance Criteria met and covered by dev/unit/property/integration tests
- [ ] System/E2E automated tests + System Test Engineer Owner Sign-off

> **_NOTE:_** Ideally, we should merge only fully implemented and tested features into the master branch.
> So all the above steps are required for the PR to be merged.
> In order to avoid the PRs becoming stale and requiring to be rebased on master, these can be merged
> after a reasonable time (current agreement is 3 days) if the System Test Engineer Owner's sign-off
> was not provided (last step in the DoD).

> **_IMPORTANT:_** Any deviation from the plan should be discussed and agreed as a comment in the Feature file.

## Sign-off

- [ ] Product Owner
- [ ] Dev Owner
- [ ] System Test Engineer Owner

# Related PRs

1. PR # here