feat: migrate @boundary annotation

[Aclrian]

Closes #1142.

Summary of Changes

• add migration for @boundary annotations to another version, with the possibilities:
  • If the mapped parameter has a number boundary and its type is known, the annotation will be migrated as expected. The interval would be converted if the type of the parameter from apiv1 and the type of the parameter from apiv2 mismatch (int, float). From a floating point boundary to an integer boundary, the boundary would be smaller. E.g., The interval (0.5, 9.5) will be converted to [1, 9]. If a conversion happens, the migrated annotation will be marked as unsure.
  • If the mapped parameter is a parameter, but its type in unknown, an unsure boundary annotation will be created for this parameter, but without any conversion.
  • If the element is not a parameter, a @todo annotation will be created.

Testing Instructions

run the migrate command or view and run the test_migration.py file

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ PYTHON	bandit	7		0	0.57s
✅ PYTHON	black	7	0	0	1.58s
✅ PYTHON	flake8	7		0	0.45s
✅ PYTHON	isort	7	0	0	1.06s
✅ PYTHON	mypy	7		0	2.67s
✅ PYTHON	pylint	7		0	2.49s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[github-actions]

🎉 This PR is included in version 1.76.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀