Optional pinning of the deployment version to the project version

[CiottiGiorgio]

This PR proposes modifying the template to allow the user to pin the deployment version to the project version.
The user would enable this feature by un-commenting a single line in deployment_config.py for each contract that they want to pin.
We resorted to reading the project version from pyproject.toml using tomllib (and not by installing an editable version in the local venv) because a TS deployer cannot access the version that way. Parsing the TOML makes more sense from a code parity standpoint.

At the point of writing this PR, the version is a string that is not used to determine if a deploy should result in an update/replace/append action.

This is still a work in progress. Items missing are:

• Version pin at project level vs per each smart contract
• Untyped dictionary from tomllib makes mypy complain
• Determine if this version pin only makes sense for non-local networks (seen as the most likely scenario for LocalNet is that people deploy a new iteration of the contract without changing the project version) (this shouldn't be an issue because the version does not influence a deploy action)
• TS deployer

[aorumbayev]

@CiottiGiorgio make sure to also regenerate example's folder ( by running poetry run pytest) which is also used as an artifacts root for snapshot testing.

[aorumbayev]

How about something like this instead

def find_pyproject_version(pyproject_toml: Path) -> str | None:
    """Finds the project version from a 'pyproject.toml' file.

    Args:
        pyproject_toml: The path to the 'pyproject.toml' file.

    Returns:
        The project version if found, otherwise None.
    """

    try:
        data = tomllib.load(pyproject_toml.open('rb'))
        return data.get('tool', {}).get('poetry', {}).get('version')
    except (FileNotFoundError, tomllib.TOMLDecodeError):
        return None 

[aorumbayev]

@CiottiGiorgio to patch last ci error make sure to run pre-commit to auto fix the code

[aorumbayev]

@CiottiGiorgio just checking in, whats the latest on the following ? Is this tracked against some reported issue? Can merge this as soon as the ci cd is fixed

[CiottiGiorgio]

Hey sorry been busy with other tasks. I plan on resuming this work next week.
Is this blocking anything?

[aorumbayev]

@CiottiGiorgio no rush, not blocking - can re review as soon as you merge conflicts