Require release identifier for each package to avoid security issues

In light of recent events with NPM it is best practice to tag the release identifier for each package to avoid any security vulnerabilities.

https://threatprotect.qualys.com/2025/09/17/more-than-400-npm-packages-affected-by-the-ongoing-supply-chain-attack/

## Current File

```
-e .

# Linter & Formatter
isort
flake8
black
mypy
pyproject-flake8
pre-commit

# Tests
coverage[toml]
pytest
pytest-sugar
dirty-equals
httpx

# Development
bpython
hatch
```

## Proposed File

```
-e .

# Linter & Formatter
isort==0.0.0
flake8t==0.0.0
blackt==0.0.0
mypyt==0.0.0
pyproject-flake8t==0.0.0
pre-committ==0.0.0

# Tests
coverage[toml]t==0.0.0
pytestt==0.0.0
pytest-sugart==0.0.0
dirty-equalst==0.0.0
httpxt==0.0.0

# Development
bpythont==0.0.0
hatcht==0.0.0
```

Review the dependency list in the issue and identify the repository file containing it. Verify the intended package names and release identifiers before changing the entries, then run the listed pytest checks and confirm the dependency installation still succeeds without altering package names.

Written by the indexing model from the issue text.