fix(docs): Correct all occurrences of toml code blocks

docs/content/developer/getting-started/create-a-package.mdx

@@ -31,7 +31,7 @@ The `Move.toml` file is the package's manifest. It describes the package and its
 In `.toml` files, use the hash mark (`#`) to denote a comment.
 :::
 
-```toml file=<rootDir>/examples/move/first_package/Move.toml
+```.toml file=<rootDir>/examples/move/first_package/Move.toml
 ```
 
 :::tip Using a local version of IOTA
@@ -54,7 +54,7 @@ of the metadata.
 The `[dependencies]` section specifies the dependencies of the project. The dependency specification can be a git
 repository URL or a path to the local directory.
 
-```toml file=<rootDir>/examples/move/first_package/Move.toml#L10-L15
+```.toml file=<rootDir>/examples/move/first_package/Move.toml#L10-L15
 ```
 
 Packages also import addresses from other packages. For example, the `Iota` dependency adds the `std` and `iota` addresses
@@ -66,7 +66,7 @@ If you have two dependencies that use different versions of the same package, yo
 the `[dependencies]` section. To do so, add the `override` field to the dependency. The version specified in
 the `[dependencies]` section will be used instead of the one specified in the dependency itself.
 
-```toml file=<rootDir>/examples/move/first_package/Move.toml#L17-L19
+```.toml file=<rootDir>/examples/move/first_package/Move.toml#L17-L19
 ```
 
 ### Dev-dependencies

docs/content/developer/iota-101/move-overview/package-upgrades/automated-address-management.mdx

@@ -30,7 +30,7 @@ Previously a `published-at` entry was **mandatory** in the `Move.toml` file, whi
 1. Delete the `published-at` line in your `Move.toml`.
 1. Set your package's address to `0x0` in the `[addresses]` section. For example:
 
-```toml
+```.toml
 [package]
 name = "Kiosk"
 
@@ -69,7 +69,7 @@ This section is an overview of the schema and internal operation of tracked addr
 
 A concrete example of the schema and state you might find in a `Move.lock` file:
 
-```toml
+```.toml
 [env]
 
 [env.testnet]

docs/content/developer/iota-101/move-overview/package-upgrades/upgrade.mdx

@@ -369,7 +369,7 @@ and updates the `UpgradeCap` with the `UpgradeReceipt` after a successful upgrad
 Let's walk through an example of developing and upgrading a package named `iota_package`.
 Initially, your manifest might look like this:
 
-```toml
+```.toml
 [package]
 name = "iota_package"
 version = "0.0.0"
@@ -499,7 +499,7 @@ Before executing the upgrade, you need to modify the package manifest:
 
 Your updated manifest should look like this:
 
-```toml
+```.toml
 [package]
 name = "iota_package"
 version = "0.0.1"
@@ -617,7 +617,7 @@ To reflect the new package ID, in the `[addresses]` section, return the `iota_pa
 Your updated manifest should look like this:
 
 
-```toml
+```.toml
 [package]
 name = "iota_package"
 version = "0.0.1"

docs/content/developer/iota-101/objects/versioning.mdx

@@ -229,7 +229,7 @@ For instance, after upgrading from version 1 to 2, you can only upgrade from ver
 
 Versioning also exists in package manifest files, both in the package section and the dependencies section. Consider the following example of manifest code:
 
-```toml
+```.toml
 [package]
 name = "some_pkg"
 version = "1.0.0"

docs/content/developer/iota-identity/getting-started/rust.mdx

@@ -24,7 +24,7 @@ To include IOTA Identity in your project, add it as a dependency in your `Cargo.
 
 This version is published to crates.io and is **stable**, following semantic versioning.
 
-```toml
+```.toml
 [dependencies]
 identity_iota = { version = "1.2.0" }
 ```
@@ -33,7 +33,7 @@ identity_iota = { version = "1.2.0" }
 
 This version matches the `main` branch of this repository. It has all the **latest features**, but as such, it **may also have undocumented breaking changes**.
 
-```toml
+```.toml
 [dependencies]
 identity_iota = { git = "https://github.com/iotaledger/identity.rs", branch = "main"}
 ```

docs/content/references/move/move-lock.mdx

@@ -17,7 +17,7 @@ If you are using source control for your package, make sure the `Move.lock` file
 
 When you build a package, the Move compiler resolves dependencies in `Move.toml`. After each resolution, the compiler writes the location of a dependency to the `Move.lock` file. If a dependency fails to resolve, the compiler stops writing to the `Move.lock` file and the build fails. If all dependencies resolve, the `Move.lock` file contains the locations (local and remote) of all your package's transitive dependencies. The `Move.lock` file stores the name and package details in an array similar to the following:
 
-```toml
+```.toml
 [[move.dependency]]
 name = “A”
 source = { git = “https://github.com/b/c.git”, subdir = “e/f”, rev = “a1b2c3” }

docs/content/references/move/move-toml.mdx

@@ -21,7 +21,7 @@ The `[package]` section contains the following information:
 
 The IOTA Move compiler creates the `[dependencies]` section for you with a single entry for the GitHub address of the IOTA network. If you need to use a local version of the network, you can edit the address to point to the local version. For example,
 
-```toml
+```.toml
 IOTA = { local = "../crates/iota-framework" }
 ```
 
@@ -31,7 +31,7 @@ You place each additional dependency your package has on a new line directly bel
 
 The IOTA Move compiler creates the `[addresses]` section for you with an entry for your package and one for the IOTA network.
 
-```toml
+```.toml
 [addresses]
 your_package_name =  "0x0"
 iota =  "0000000000000000000000000000000000000000000000000000000000000002"