Speedup test collection for tests/www

[insomnes]

• Remove initial_db_init call from top level of tests/www/views/test_views_rendered.py.
• Misc: Move overlooked tests/utils/test_dataform.py to providers/google/tests/unit/google/cloud/utils/test_dataform.py

This call significantly slows tests collection.
I was able to drop arbitrary collection time with --collect-only for www tests from 20 to 5-6 seconds. And the whole tests collection from 41-42 to 32-33 seconds. Fast test collection allows various opportunities like dependencies smoke-tests and improves developers' experience.

This call is already provided by tests_common.pytest_plugin, so it should not affect the tests.

---

^ 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.

[insomnes]

I must mention that I am quite confused by test_rendered_task_detail_env_secret.
I am unsure if I've understood it correctly and if my fixes are right.

In its initial configuration this test depends on parametrized parameters call order cause otherwise monkey would not be marked as secret. So I am also unsure that the test in its original config is right.

[potiuk]

NICE!

[potiuk]

I must mention that I am quite confused by test_rendered_task_detail_env_secret. I am unsure if I've understood it correctly and if my fixes are right.

In its initial configuration this test depends on parametrized parameters call order cause otherwise monkey would not be marked as secret. So I am also unsure that the test in its original config is right.

Not 100% sure either. But since tests/www will be deleted soon together with the old UI, I woudl not worry too much about it.

[insomnes]

But since tests/www will be deleted soon together with the old UI, I woudl not worry too much about it.

That's awesome! The test collection there is one of the longest. I was researching what's going on with it but decided to postpone a deep investigation because of all 3.0 changes and to fix only this "low-hanging fruit." Even the first phase of old provider code cleanup made a huge difference.

Thank you!