Split utils sh

[potiuk]

Please take a look at the last commit. It is based on #9130

---

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 backward-incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

[potiuk]

Following the discussion with @dimberman (and recent slack conversation with @ashb about utils as being bad name) -> I split the _utils.sh into meaningful and much smaller libraries - each responsible for pretty much one thing only.

It should be much easier to understand what's going on and where to search for corresponding part of the bash script. If we ever decide to reimplement some parts of it in a different languages, that might also be good idea to understand what Breeze and the scripts are actually doing.

[dimberman]

Thank you @potiuk!

[dimberman]

@potiuk we probably want to run all tests on this btw.

[potiuk]

@potiuk we probably want to run all tests on this btw.

Good point. I updated the pattern in ci.yml to also trigger test builds on any change in "scripts" :).