[#14361] Adding new generator for configuration based source template

[brianjlai]

What

Add a new template to ./generator.sh that allows developers to instantiate a new configuration based source connector. This automatically generates the source yaml parser and a limited set of components to get a basic connector working.

• a single stream
• basic schema_loader
• a requester with no pagination defined
• mocked out authentication, url_base, primary_key, path, and record selector

After generating the boilerplate, the remaining requirements for the implementer are as follows:

• Implement spec.yaml
• Add stream schemas to /schemas
• Adding testing config.json
• Replace url_base, token, path

How

Adapts the existing http-source generator, but the key areas it diverges is in how source.py is implemented in order to parse a YAML file into a fully functioning source that adheres to the CDK interface. It also defines the baseline YAML config.

Recommended reading order

1. plopfile.js
2. source.py.hbs
3. {{snakeCase name}}.yaml.hbs
4. README.md.hbs
5. schemas/TODO.md.hbs
6. I also fixed a few small CDK things to make the template cleaner

[girarda]

is there a way to always get the latest version when running the generator?

[brianjlai]

Do we always want the latest bumps in major versions too? The ~= should continue to get the latest patch. I can see extending this out to the minor version, but we may still want to be restrictive against getting the latest when theres a major version bump.

[girarda]

I think it's fine to freeze the requirements, but i would expect the generator to create a connector using the latest version of the cdk

[brianjlai]

looking into it a bit, it is possible since we could parse the cdk's setup.py file to find the latest, but I don't see a great way of doing that. maybe some derivative of using the setuptools package, but that normally gets the current working version. Not super blocking so I'm gonna move forward with merging it in.