## Motivation
The single quote escaping syntax used in GHA workflow to run `airbyte-ci` was wrong.
Separating `schedule` triggers from `workflow_dispatch` triggers makes it easier to get the syntax right.
### Workflow and Command Updates:
* [`.github/workflows/connectors_up_to_date.yml`](diffhunk://#diff-2d17c6d9c0d58a040bfab9725e36051d4330b78f1a76e2f9fb024f673b7a74d4L14-R14): Added a new metadata query to exclude `source-declarative-manifest` from the `connectors-options` input. Updated the workflow to handle both `workflow_dispatch` and `schedule` events separately. [[1]](diffhunk://#diff-2d17c6d9c0d58a040bfab9725e36051d4330b78f1a76e2f9fb024f673b7a74d4L14-R14) [[2]](diffhunk://#diff-2d17c6d9c0d58a040bfab9725e36051d4330b78f1a76e2f9fb024f673b7a74d4L28-R30) [[3]](diffhunk://#diff-2d17c6d9c0d58a040bfab9725e36051d4330b78f1a76e2f9fb024f673b7a74d4L42-R59)
### Documentation Changes:
* [`airbyte-ci/connectors/pipelines/README.md`](diffhunk://#diff-62eccd92928fbcd3d285983bfdaa2b0d4ca49016cb9c2f63d6d9fc968c59c541L528): Removed the `--ignore-connector` option from the documentation and added an entry to the changelog explaining the removal. [[1]](diffhunk://#diff-62eccd92928fbcd3d285983bfdaa2b0d4ca49016cb9c2f63d6d9fc968c59c541L528) [[2]](diffhunk://#diff-62eccd92928fbcd3d285983bfdaa2b0d4ca49016cb9c2f63d6d9fc968c59c541R853)
### Codebase Simplification:
* [`airbyte-ci/connectors/pipelines/pipelines/airbyte_ci/connectors/up_to_date/commands.py`](diffhunk://#diff-e6ca381b7841536a83b88d6b45f24bbcdbe304f88248787054817373d8f73544L52-L57): Removed the `--ignore-connector` option and its related logic from the `up_to_date` command. [[1]](diffhunk://#diff-e6ca381b7841536a83b88d6b45f24bbcdbe304f88248787054817373d8f73544L52-L57) [[2]](diffhunk://#diff-e6ca381b7841536a83b88d6b45f24bbcdbe304f88248787054817373d8f73544L66-L75)
### Version Bump:
* [`airbyte-ci/connectors/pipelines/pyproject.toml`](diffhunk://#diff-087e2c37602bbd6824f875004abddcb4e1a374da12bf84201671ed0900882ce0L7-R7): Updated the version from `4.41.6` to `4.41.7`.
## What
The Dagger team created a bunch of additional token to use their distributed cache.
We want multiple token to "namespace" the cache per use case so that for instance `airbyte-ci format` can pull the couple images it uses from it, instead of downloading the full cache which has all the connector testing related layers.
Rationale:
* `DAGGER_CLOUD_TOKEN_CACHE_5`: internal python packages testing
* `DAGGER_CLOUD_TOKEN_CACHE_4`: community CI only
* `DAGGER_CLOUD_TOKEN_CACHE_3`: connector build/testing/publish
* `DAGGER_CLOUD_TOKEN_CACHE_2`: light jobs like `format` or `version increment check`
