chore: add manifest.json to source tree?

[mikeshultz]

I'm not entirely versed in the reasons why this file is handled the way it is, but I'm wondering if it would be beneficial to just add it to the python sdk source tree. The file is unlikely to change unless we alter the contract which seems unlikely without a version split, at least.

This also makes using a repo def cleaner. For instance:

apepay = { git = "https://github.com/ApeWorX/ApePay.git" }

Doesn't exactly work.

Maybe there's an alternative to having the project build include the compilation and copy but that seems extreme. Thoughts?

[fubuloubu]

still haven't really figured out a good way to bundle the manifest with a python package so that SDKs work out of the box without needing to compile things