Fix RecursionError in common.compat hook lineage add_extra polyfill

[kaxil]

Summary

On Airflow < 3.2, common.compat's get_hook_lineage_collector() polyfills add_extra by
monkeypatching the collected_assets and has_collected class properties of the lineage
collector. _add_extra_polyfill was not idempotent: the trigger gate (_lacks_add_extra_method)
checks instance-level _extra, so a fresh collector instance of an already-patched class
re-enters the polyfill and re-wraps the class property, capturing the previously installed wrapper
as the "original". Each call stacks another layer onto the getter chain, so once enough collectors
are created the next collected_assets / has_collected access exceeds the recursion limit and
raises RecursionError.

Where it shows up

In production the global collector is a process singleton (the accessor is @cache-decorated) and
the polyfill only runs on Airflow < 3.2, so it is applied exactly once -- no impact. The failure
surfaces on the Compat 3.1.x provider test matrix, where a fresh HookLineageCollector is built
per test: the class accumulates one wrapper per test until the lineage edge-case tests blow the
recursion limit. This is a test-suite/robustness fix, not a production incident.

Fix

Capture the collector's true original collected_assets / has_collected getters once per class
(stashed in the class's own __dict__) and always wrap that original, rather than whatever getter is
currently installed:

• The polyfill is re-applied for every fresh collector instance, and on Airflow 2 the asset-naming
  layer re-patches collected_assets before each call. Wrapping the current value would capture the
  previous compat wrapper as the "original", so the getter chain grew one layer per call until access
  hit the recursion limit.
• Wrapping the stored original instead keeps the chain flat (depth one) no matter how many times the
  polyfill runs, while still re-applying the extra wrapper each call -- so it composes correctly
  with the Airflow 2 asset-naming layer that re-patches collected_assets.
• The stash is keyed on the class's own __dict__, so a subclass that overrides these properties is
  captured in its own right rather than reusing a base class's original.
• Instance _extra / _extra_counts are initialized only when missing, so re-applying never clears a
  collector that already accumulated extras.

Behavior is otherwise unchanged: every collector still gets add_extra and the extended
collected_assets / has_collected.

[kacpermuda]

Thanks Kaxil for fixing this, missed that for sure when writing tests