fix(docs): replace version variables with hardcoded verisons (#1301)

While FuelLabs/fuels-rs#1168 is unfinished, we
should hardcode the used versions in the documentation URLs.

Please note that this PR:
- does **NOT** address #1168
- requires incorporating the updating of versions in the changed files
on each release. @digorithm

### Checklist
- [x] I have linked to any relevant issues.
- [x] I have updated the documentation.
- [x] I have added tests that prove my fix is effective or that my
feature works.
- [x] I have added necessary labels.
- [x] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [x] I have requested a review from the relevant team or maintainers.

docs/src/connecting/retrying.md

@@ -1,6 +1,6 @@
 # Retrying requests
 
-The [`Provider`](https://docs.rs/fuels/0.47.0/fuels/accounts/provider/struct.Provider.html) can be configured to retry a request upon receiving a `io::Error`.
+The [`Provider`](https://docs.rs/fuels/0.62.0/fuels/accounts/provider/struct.Provider.html) can be configured to retry a request upon receiving a `io::Error`.
 
 > Note: Currently all node errors are received as `io::Error`s. So, if configured, a retry will happen even if, for example, a transaction failed to verify.
 

docs/src/getting-started.md

@@ -82,10 +82,10 @@ cargo test -- --nocapture
 Add these dependencies on your `Cargo.toml`:
 
 ```toml
-fuels = "{{versions.fuels}}"
+fuels = "0.62.0"
 ```
 
-> **Note** We're using version `{{versions.fuels}}` of the SDK, which is the latest version at the time of this writing.
+> **Note** We're using version `0.62.0` of the SDK, which is the latest version at the time of this writing.
 
 And then, in your Rust file that's going to make use of the SDK:
 

docs/src/types/asset-id.md

@@ -1,6 +1,6 @@
 # `AssetId`
 
-Like `Bytes32`, `AssetId` is a wrapper on `[u8; 32]` with similar methods and implements the same traits (see [fuel-types documentation](https://docs.rs/fuel-types/{{versions.fuel-types}}/fuel_types/struct.AssetId.html)).
+Like `Bytes32`, `AssetId` is a wrapper on `[u8; 32]` with similar methods and implements the same traits (see [fuel-types documentation](https://docs.rs/fuel-types/0.49.0/fuel_types/struct.AssetId.html)).
 
 These are the main ways of creating an `AssetId`:
 

docs/src/types/contract-id.md

@@ -1,6 +1,6 @@
 # `ContractId`
 
-Like `Bytes32`, `ContractId` is a wrapper on `[u8; 32]` with similar methods and implements the same traits (see [fuel-types documentation](https://docs.rs/fuel-types/{{versions.fuel-types}}/fuel_types/struct.ContractId.html)).
+Like `Bytes32`, `ContractId` is a wrapper on `[u8; 32]` with similar methods and implements the same traits (see [fuel-types documentation](https://docs.rs/fuel-types/0.49.0/fuel_types/struct.ContractId.html)).
 
 These are the main ways of creating a `ContractId`: