feat: VCS versioning and mypy

[Saransh-cpp]

VCS versioning by default for the project and the template.

mypy for the project (I think adding an option for the template would make this PR huge, but I'll add it through another PR 🙂)

[agriyakhetarpal]

Wow nice there are a lot of changes. Making mypy optional in the template would be great, especially because we were not using it for the project (should we do that?). Also, could you clarify if there will be changes on how we update versions while making a release with the addition of hatch-vcs—is there anything to keep in mind after one updates the version in __init__.py, because I read it uses timestamps from version control systems? That way I will include relevant resources when I prepare the documentation for using the template. Thanks for doing this, @Saransh-cpp!

[Saransh-cpp]

especially because we were not using it for the project (should we do that?)

This PR adds mypy for the project!

Also, could you clarify if there will be changes on how we update versions while making a release with the addition of hatch-vcs—is there anything to keep in mind after one updates the version in init.py

Create a new release on GitHub and done 🙂

hatch-vcs will automatically fetch that git tag and bump the version. Or, if you are working locally, create a new git tag and that is your new version!

[agriyakhetarpal]

That sounds great, will simplify a lot of things. The changes look good to me, feel free to merge whenever

[Saransh-cpp]

Thanks for the review! Merging.