Add forward-compatibilty test and fix for using old client on new node (#3281)

## Linked Issues/PRs
<!-- List of related issues/PRs -->

## Description
<!-- List of detailed changes -->

We are addressing a problem with forward-compatibility in our fuel-core
client. We have recently added new consensus parameter versions and if
users haven't updated their client to support the new parameters, it is
just going to error. We want to prevent this from happening with the
following changes:

This PR does two things
1. It changes the way that the graphql server handles requests for
consensus parameters. If you ask for params but don't specify any V2
parameters, then it will assume you are querying from a client that only
supports V1 params and will convert V2 parameters to V1 before returning
2. Change the way the client works so if it receives unsupported
consensus parameters in the future, it will emit and error and convert
to the latest consensus parameter version optimistically.

## Checklist
- [ ] Breaking changes are clearly marked as such in the PR description
and changelog
- [ ] New behavior is reflected in tests
- [ ] [The specification](https://github.com/FuelLabs/fuel-specs/)
matches the implemented behavior (link update PR if changes are needed)

### Before requesting review
- [ ] I have reviewed the code myself
- [ ] I have created follow-up issues caused by this PR and linked them
here

### After merging, notify other teams

[Add or remove entries as needed]

- [ ] [Rust SDK](https://github.com/FuelLabs/fuels-rs/)
- [ ] [Sway compiler](https://github.com/FuelLabs/sway/)
- [ ] [Platform
documentation](https://github.com/FuelLabs/devrel-requests/issues/new?assignees=&labels=new+request&projects=&template=NEW-REQUEST.yml&title=%5BRequest%5D%3A+)
(for out-of-organization contributors, the person merging the PR will do
this)
- [ ] Someone else?