[Docs]: Make Rust docs consistent

[bidzyyys]

What is the feature you would like to see?

Rust docs for our contracts should follow the order:

1. General information about the function
   1.1 Additional NOTE: ...
   1.2 Additional NOTE: "In order to expose this function in ABI you need to ..."
2. Arguments (listed with *)
3. Errors (listed with *)
4. Panics (listed with *)
5. Example (if 1.2 exists)

Contribution Guidelines

• I agree to follow this project's Contribution Guidelines

[0xNeshi]

Just for clarity, with the proposed convention the Erc721::token_uri docs would look like below?

    /// Returns the Uniform Resource Identifier (URI) for `token_id` token.
    ///
    /// NOTE: In order to expose this function in the ABI, you need to annotate
    /// it with `#[selector(name = "tokenURI")]` and ensure that the `erc721`
    /// parameter is passed internally. This design works around Stylus's lack
    /// of inheritance while avoiding code duplication. See the Example section.
    ///
    /// # Arguments
    ///
    /// * `&self` - Read access to the contract's state.
    /// * `token_id` - ID of a token.
    /// * `erc721` - Read access to a contract providing [`IErc721`] interface.
    ///
    /// # Errors
    ///
    /// * [`Error::NonexistentToken`] - If the token does not exist.
    ///
    /// # Example
    ///
    /// ```rust,ignore
    /// #[selector(name = "tokenURI")]
    /// pub fn token_uri(&self, token_id: U256) -> Result<String, Vec<u8>> {
    ///     Ok(self.metadata.token_uri(token_id, &self.erc721)?)
    /// }
    /// ```

[bidzyyys]

Yes @0xNeshi 💯