updated setup.py template to read setup metadata from existing json/yaml files.

[JosephHobbs]

I noticed in the latest version of the SDK that it was reading the version file from the extension.yaml file. My thought was, why not read the other parameters from the extension.yaml activationSchema.json files too? This eliminates the need to duplicate things like author, version, etc...

[dlopes7]

This looks cool, but unfortunately we can't accept this as certain internal tools we use such as snyk would be unable to parse the setup.py file

When it parses it, it doesn't have access to the extension.yaml file and all of these would break.

[dlopes7]

We also can't add pyyaml as a dependency to every extension

[JosephHobbs]

I only used PyYaml because it's already a dependency in the SDK

[dlopes7]

Yes but adding it to setup.py makes it a requirement on the final extension build

The AG and OA won't have pyyaml and won't be able to install the extension

[JosephHobbs]

Ok, so what if I...

• Drop the dependency on PyYaml and take an approach similar to find_version() by parsing it myself.
• Use the same catch/pass approach and return sensible defaults to account for when extension.yaml and activationSchema.json are not present.

Would that be valuable/acceptable?