Ensure details panel is shown when any tab is selected

[Usiel]

closes #34132

When creating the feature request I was only thinking of the Graph tab. However, while playing with this I realized that whenever tab is set, the user will expect to see the details panel and the requested tab.

There are 2 main scenarios where a user would navigate to a link with the tab query param set:

1. User clicks on one of the pills on the DAG view (Graph, Gantt, Code). Imo, the user will expect to see the relevant tab in the details panel, even if they have hid it previously.
2. User clicks on a link (e.g. from DAG runs, or someone sharing a link). Less clear cut than scenario 1, but still I think the most user friendly result is to show the requested tab (in the details panel).

The behavior is so that we do not change the user's setting, if they go back to the grid view the details panel will be hidden if that was their original setting.

I think there is still room for improvement, the UI feels slightly inconsistent due to the different methods of achieving the same state. This PR is just a tiny change to (hopefully) make this a bit less confusing to the user.

---

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

[bbovenzi]

Good idea. I wonder if we want to get rid of the localStorage part of this then.

Also, mind to double check lint and type checks?

[Usiel]

Good idea. I wonder if we want to get rid of the localStorage part of this then.

Hmm I was wondering if this was a remnant of a full page reload or similar, but after looking at #22123 I don't think that's the case. I think it would be fine to remove the localStorage usage and also not to remember this at all (-> revert back to showing the panel on a reload), but then again I never hid the panel on purpose, so maybe I'm not the target audience 😄

Also, mind to double check lint and type checks?

I reran the "Static checks" step (breeze static-checks --all-files --show-diff-on-failure --color always --initialize-environment) locally, all green here.
(The GitHub actions run failed due to timeout: "The job running on runner GitHub Actions 69 has exceeded the maximum execution time of 30 minutes.")