Update pre-commit-hooks repo version

[feluelle]

• use official isort pre-commit-hook
• use official yamllint pre-commit-hook
• run isort pre-commit-hook on all python files instead of files ending with py

---

Make sure to mark the boxes below before creating PR: [x]

• Description above provides context of the change
• Unit tests coverage for changes (not needed for documentation changes)
• Target Github ISSUE in description if exists
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions.
• I will engage committers as explained in Contribution Workflow Example.

---

In case of fundamental code change, 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 UPDATING.md.
Read the Pull Request Guidelines for more information.

[feluelle]

pre-commit/pre-commit-hooks now requires python3.6.1+

That is the only noticeable difference for us.

Ref: https://github.com/pre-commit/pre-commit-hooks/releases

[feluelle]

Fix version - I set it to the latest version.

[feluelle]

Fix version - I set it to the latest version.

[potiuk]

It looks like the new stylelint requires some style improvements as well @feluelle

[ashb]

isort seems to be wreaking havok with the UPDATING.md -- we might have to not pick the latest version (or else turn it tune it down):

diff --git a/docs/howto/operator/gcp/gcs_to_gcs.rst b/docs/howto/operator/gcp/gcs_to_gcs.rst
index e17bedf..bb3fda1 100644
--- a/docs/howto/operator/gcp/gcs_to_gcs.rst
+++ b/docs/howto/operator/gcp/gcs_to_gcs.rst
@@ -40,11 +40,9 @@ perform this task faster and more economically. The economic effects are especia
 Airflow is not hosted in Google Cloud Platform, because these operators reduce egress traffic.
 
 These operators modify source objects if the option that specifies whether objects should be deleted
-from the source after they are transferred to the sink is enabled.
 
 When you use the Google Cloud Data Transfer service, you can specify whether overwriting objects that already exist in
 the sink is allowed, whether objects that exist only in the sink should be deleted, or whether objects should be deleted
-from the source after they are transferred to the sink.
 
 Source objects can be specified using include and exclusion prefixes, as well as based on the file
 modification date.

It seems to think any line starting with from is an import line! We need to only have it operate on .py files

[feluelle]

Thanks all - will fix the issues.

[feluelle]

It seems to think any line starting with from is an import line! We need to only have it operate on .py files

4.3.21 fixed it.
4.3.21-2 broke it.
develop has the correct version, but it is not released yet. So I added it here and use 4.3.21-2 so we have the latest version of isort.