feat: migrate @CalledAfter annotations

[Aclrian]

Closes #1150.

Summary of Changes

• Migration of @CalledAfter annotations through a mapping from old api elements to new api elements for the two function called before or after.
  If there is no mapping from the function called before to another function in the class of the apiv2 element, an unsure @CalledAfter annotation will be created with the same name as the function called before.
  Else, a @CalledAfter annotation will be created, if the called before function is mapped to only one other function and the annotated apiv2 element is a function.
  Otherwise, mark the mapped apiv2 elements with a @todo annotation.

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	9		0	0.66s
✅ PYTHON	black	9	0	0	1.54s
✅ PYTHON	flake8	9		0	0.52s
✅ PYTHON	isort	9	0	0	0.91s
✅ PYTHON	mypy	9		0	3.1s
✅ PYTHON	pylint	9		0	2.9s

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.80.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀