Move black parameters to pyproject.toml
# What does this PR do ?

Move `black` formatter parameters to `pyproject.toml`

Advantages:
- parameters are stored in one place
- one can use `black .`/`black <file>` command to reformat code
- more robust: if someone tries to reformat code with the newest `black` version, the error will be thrown (instead of reformatting the whole codebase)

**Collection**: [Note which collection this PR will affect]

# Changelog 
- add `black` params to `pyproject.toml`
- remove params from `setup.py` and `.pre-commit-config.yaml`

# Usage
* You can potentially add a usage example below

```
black .
black edited_file.py
```

# Before your PR is "Ready for review"
**Pre checks**:
- [x] Make sure you read and followed [Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md)
- [ ] Did you write any new necessary tests?
- [ ] Did you add or update any necessary documentation?
- [ ] Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  - [ ] Reviewer: Does the PR have correct import guards for all optional libraries?
  
**PR Type**:
- [x] New Feature
- [ ] Bugfix
- [ ] Documentation

If you haven't finished some of the above items you can still open "Draft" PR.


## Who can review?

Anyone in the community is free to review the PR once the checks have passed. 
[Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md) contains specific people who can review PRs to various areas.

# Additional Information
* Related to # (issue)
