Source GoogleAds: add end_date to config

[iberchid]

What

Relates to issue #8666

How

Added end_date to spec and updated the source.py and streams.py files to allow for setting an end_date.

Recommended reading order

1. spec.json
2. source.py
3. streams.py

🚨 User Impact 🚨

No changes, because when the parameter is not provided the default value is used which is identical to the previous implementation.

Pre-merge Checklist

Expand the relevant checklist and delete the others.

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Secrets in the connector's spec are annotated with airbyte_secret
• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
• Code reviews completed
• Documentation updated
  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
• PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• Credentials added to Github CI. Instructions.
• /test connector=connectors/<name> command is passing.
• New Connector version released on Dockerhub by running the /publish command described here
• After the new connector version is published, connector version bumped in the seed directory as described here
• Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here

Connector Generator

• Issue acceptance criteria met
• PR name follows PR naming conventions
• If adding a new generator, add it to the list of scaffold modules being tested
• The generator test modules (all connectors with -scaffold in their name) have been updated with the latest scaffold by running ./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates then checking in your changes
• Documentation which references the generator is updated as needed.

---

This change is 

[CLAassistant]

All committers have signed the CLA.

[marcosmarxm]

See comments.

[marcosmarxm]

@iberchid please run unit tests to validate your change also please add a new unit test with a specific end_date to validate your changes.

[marcosmarxm]

@sherifnada can you review the UX modification this PR makes?

[iberchid]

Hi @marcosmarxm , Thanks for your comments, I updated the scripts according to your recommendations. I also ran existing unit tests and added a few more:

[marcosmarxm]

@iberchid can you solve the conflicts and make sure the ./gradlew airbyte-integrations:connectors:source-google-ads:integrationTest is working?

[marcosmarxm]

@iberchid can you solve the conflicts? and share the output from the command above

[iberchid]

Hello @marcosmarxm , I resolved the conflicts and reran the unit tests both in .venv and gradle, below is the output.

1-Locally in .venv : The test test_streams_count failed in test_source.py , which expected result was changed here. The remaining tests passed.

2- Gradle: The failures are related to secrets/config.json, these tests, added in this commit, use the config.json file, which cannot be accessed with Gradle. The remaining tests passed.

[marcosmarxm]

You need to create a folder called secrets and add a file inside with the config to run integration tests and check connection.

[iberchid]

Here it is @marcosmarxm :

[iberchid]

Hi @marcosmarxm , what is the status of this PR? Are there any other TODOs left for me?