Extend Papersurvey connector to support syncing an individual survey's questions, and a subset of surveys' responses

[qixotic]

(Opening a PR just for @siddhant3030 to see the use case)

What

Using Airbyte's no-code builder, we've added the streams:
survey_questions - https://api.papersurvey.io/surveys/{{stream_partition.manual_survey}} - pulls survey meta data + questions
entries_manual - https://api.papersurvey.io/surveys/{{stream_partition.manual_survey}}/entries - supports incrementally syncing responses for a subset of survey ids.

How

Config params:
survey_ids list of ids from the user for static partitioning of the surveys to sync over. Used by both streams above right now. entries_manual is a separate stream from the one that syncs over everything (entries).

A few caveats w/ airbyte:

• You can't allow a user to conditionally partition streams dynamically or statically in the same stream definition, resulting in the need to essentially have a duplicate stream of the same object type that gets synced, in order to have different configurability.
• user variables in stream definitions require configuring those values when setting up the source in Airbyte. If you want to sync using an additional different set of values, you need to set up a new source for that.

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.