Add AWS AppConfig API Data Source

[snowe2010]

Proposed changes

Add an AWS AppConfig API Data Source

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put an x in the boxes that apply.

• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.

We need an AppConfig data source, and this was a simple addition alongside the lambda, dynamo, and athena plugins.

• Add an AWS AppConfig API Data Source with several query options. Not all
  are implemented, but most of the main ones are.
• Small fix to add 'no' option to list

[netlify]

👷 Deploy request for lowcoder-cloud pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	278ad55

[netlify]

👷 Deploy request for lowcoder-test pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	846f576

[FalkWolsky]

Could we ask you to prepare a small Postman Collection and add it instead of the api-examples? That would allow us to create soon a Lowcoder Workspace on Postman and collect all such API calls as demonstration. We think it would be more visible...

[snowe2010]

I'm not actually sure I can, Postman refuses to let me sign in anymore. It's been broken since they changed from being a free service to mostly paid. :/

My team at work entirely switched to using the HTTP file standard which means you can easily store and run your collections directly from your IDE rather than in a proprietary software. It's worked out quite well. But yeah, it's definitely not as popular as Postman though :(

[snowe2010]

Yeah I'm unable to sign in, so I can't save any requests so I can't export anything :(. I can remove the file if you don't want http files in the codebase, though I think they're much more open source friendly.

[FalkWolsky]

We love your contribution a lot, so we merge it now.
The api-examples file we may exchange with a Postman Collection later. As for now, we think you are right so we take it into the change. Thank you very much for your valuable contribution!!