Remove dependency on special tests for tests finalization

[potiuk]

Tests finalization is run generally when all tests succeded in canary run. What the finalization does is:

• updating constrainst
• pushing them
• updating image cache
• summarizing warnings

However special tests are really to test some special cases - back compatibility, lowest dependencies, latest boto etc. All those tests will only be run in a few selected PRs where we upgrade dependencies and they will not affect "regular" PRs, so we can safely update the constraints and update the cache without waiting for special tests.

This will increase the frequency of updates to constraints - because now they might be quite delayed in case some special tests fail, but this is unnecessary holding the constraints update.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

This should help with much more frequent refresh of constraints and update - they were impacted by stability of special tests so far, but this was not really necesary.