Improve node incompatibility warnings

[arboleya]

Note

Incoming from the forum:

• https://forum.fuel.network/t/fuels-typescript-sdk-error/5266

---

We do have checks in place, but we call fetchChain before the check occur.

A possible solution would be to make an additional request only for the node's version before the rest.

It requires some consideration. Also, we'd need to cache this result to avoid unnecessary requests.

[nedsalk]

I'm not sure if it makes sense anymore to do this now that fuel-core releases are backwards compatible and errors such as the one reported in the forum post shouldn't be happening anymore. This would mean an additional request towards the network whenever a Provider.create call is done for the first time and I don't think it's worth it. @FuelLabs/sdk-ts

If anything, it doesn't look like a p0 issue anymore but a p2.

[arboleya]

Makes sense — priority decreased.

[arboleya]

We should keep it because things like the [graphql] API can change and break stuff.

Better have a warning to be safe.