Thanks

* Update the release process.

* Fix conflics, small update

* Update go release process link with the newly added resource

The "SKIP_PROVIDER_TESTS" was added as quick-fix when releasing
2.5.0 release, now we can make it a bit more consistent with
all other selective checks. It has now unit tests covering it
and it is produced as selective-checks output so that we do not
have to encode the logic in conditions in the ci.yml.

A long time ago in a galaxy far away ...

We had a code that make our CI variables independent from the
CI Actions used and we used CI_* prefixes to distinguish those
values. This reflected the time when we moved from Travis to
GitHub Actions and we wanted to keep the possibility to support
both. Those variables have been since removed, but there was
that one single planet (err. script) where the remnant of the old
Jedi order (err. variables) remained and they caused rather
meaningless commit messages for constraints.

This PR updates the commit messages to be more meaningful,
including direct links to the action that updated the constraints
and helpful description on how you can easily run breeze with the
exact set of dependencies that were used for it.

This docstring is no longer correct (since 2.0) and should be removed

Co-authored-by: Bas Harenslak <BasPH@users.noreply.github.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>

The recent change #29080 introduced missing black import in the
pre-commit that run the compilation. The compilation happened in
the background thread and it's ouptut was only visible in the
asset_compilation output file

This PR fixes the black import problem by removing unnecessary import,
but it will also stop start-airflow and exit with error as well as
surface the output of asset compilation to the console.

When Breeze is stoped, by default all volumes created are removed,
unless you specify `--preserve-volumes`. The "mypy-cache-volume"
was not removed because it is not created by docker-compose.

This change adds a command to remove it in breeze stop unless
`--preserve-volumes` is used.

shorten sleep time on athena sys test. 2 minutes faster.

set shorter polling times of fast ops in batch sys test - 4min faster

shorter polling on cloudformation systest - 1min30s faster

shorter polling time on lambda sys test - 1 min faster

shorter wait on quicksight

shorter waits for sagemaker test

shorten wait time for setp_functions, 50s faster

shorter wait on dms. This one is important so that we don't miss the running status

set sleep times out of doc

Bumps [ua-parser-js](https://github.com/faisalman/ua-parser-js) from 0.7.31 to 0.7.33.
- [Release notes](https://github.com/faisalman/ua-parser-js/releases)
- [Changelog](https://github.com/faisalman/ua-parser-js/blob/master/changelog.md)
- [Commits](https://github.com/faisalman/ua-parser-js/compare/0.7.31...0.7.33

)

---
updated-dependencies:
- dependency-name: ua-parser-js
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* use ecr hook to get credentials

* make error message less confusing

Co-authored-by: Beata Kossakowska <bkossakowska@google.com>

This isn't in a release yet, so let's take the opportunity to fix the
naming of the kwarg.

This is useful to use one command to generate issues for all our releases.

* Keyfile dict can be dict not str

This makes it much easier to define a connection with json.  We can do this:

```json
{"extra": {"keyfile_dict": {"foo": "bar", "private_key": "hi"}}}
```

Instead of this:

```json
{"extra": {"keyfile_dict": "{\"foo\": \"bar\", \"private_key\": \"hi\"}"}}
```

I.e. instead of json-dumping the contents of the key first, we can just paste the key as is into the "keyfile_dict" field in extra.

Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>

The biggest change here is using `State` or `TaskInstanceState` where
appropriate. Even though their strings are the same, it provides useful
context, so we should use the correct enum.

One could argue `State` isn't the right thing to use, but at least it's
consistently wrong now :)

* move fix to ready_to_reschedule
* replace check on debug exec with new property

Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>

* accept either dict of list for tags