Jl/fix style

[jordlay]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[patrykkulik-microsoft]

There are a few weird docstrings in the codebase which your linting seems to ignore. For example in custom.py:

``
Publish a generated definition.

:param cmd: :param client: :type client: HybridNetworkManagementClient :param
definition_type: VNF or CNF :param config_
file:
Path to the config file for the NFDV    :param definition_file: Optional path to a
bicep template to deploy, in case the user                       wants to edit the
built NFDV template. If omitted, the default                       built NFDV
template will be used.    :param parameters_json_
file:
Optional path to a parameters file for the bicep file,                      in case
the user wants to edit the built NFDV template. If                      omitted,
parameters from config will be turned into parameters                      for the
bicep file    :param manifest_
file:
Optional path to an override bicep template to deploy
manifests    :param manifest_parameters_json_
file:
:param cmd:
:param client:

``