Rename columns to valid namedtuple attributes + ensure Row.fields are retrieved as tuple

[Joffreybvn]

Fix for #36839, #36838 and a similar issue in the ODBCHook.

With this PR:

• When columns are named with a reserved Python keywords, or contains invalid characters (like ( or @) that cannot be used in an attribute name, the columns get renamed.
• The fields attribute is retrieved as tuple even when the Databricks.Row object is created in two steps.

Note: Having columns being rename is not an issue, as users should use the tuple API. Namedtuple is there for backward compatibility during the transition to tuples.

---

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

[Joffreybvn]

ODBCHook has the same issue (#36838). But it's a typing.NamedTuple there (instead of a collection.namedtuple). Which do not support rename=True. Thus I'll refactor the hook to use the collection.namedtuple too.