Refactor: Consolidate 'import textwrap' in core

[eumiro]

No description provided.

[Lee-W]

I'm a bit curious about why we want to do it this way. Also, would it make sense if we document these changes somewhere in the contribution document so that newcomers know what to follow?

[eumiro]

I'm a bit curious about why we want to do it this way. Also, would it make sense if we document these changes somewhere in the contribution document so that newcomers know what to follow?

Grepping and counting for imports of textwrap shows:

 11 from textwrap import dedent
3 from textwrap import wrap
37 import textwrap

the majority imports textwrap directly, so I am suggesting to do it so everywhere.

[Lee-W]

I'm a bit curious about why we want to do it this way. Also, would it make sense if we document these changes somewhere in the contribution document so that newcomers know what to follow?

Grepping and counting for imports of textwrap shows:

 11 from textwrap import dedent
3 from textwrap import wrap
37 import textwrap

the majority imports textwrap directly, so I am suggesting to do it so everywhere.

Yep, sounds reasonable

[eladkal]

Can you please split this PR to 2 PRs (and possibly all other refactoring):

1. airflow/providers changes
2. all the rest

it would make things easier for release managers as providers releases are separated from airflow core