feat: allow existing configs [APE-836]

fixes: #11 fixes: #109 Couldn't find a linear ticket!

See questions below, especially the last one.

Check for either an existing JS or TS Hardhat config file
If one exists, don't create the other (so now TS is supported basically)
If one exists and we detect some missing necessary properties, we raise a big loud warning so it is known.

Questions about how to further improve:

I personally think generating or adding support for generating a the Typescript config is out-of-scope because of the additional dependencies typescript uses as well as the additional config files (tsconfig.json). It seems better left up to the user if they require such a complex setup. Thoughts?
An alternative to only showing a warning, we could generate a default config file in the .ape directory somewhere and reference it using the --config option. This would eliminate the need to interfere with the user's project at all. Downside is that the wouldn't be able to configure it at (but we could add everything to ape-config.yaml and stuff) and that their ape with differ from their hardhat. Upside, we'd just work and if they were using brownie or something, that artifact wouldnt affect.

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

ApeWorX / ape-hardhat