Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

This how the logout button shall look in the GUI:

GUI with the new Logout button:

GUI after removing additional "login" text:

The current fix is not a clean one. I did go through the code to make a cleaner fix which would involve including the "logout" in one of the functions in
base_auth_manager.py:

    def filter_permitted_menu_items(self, menu_items: list[MenuItem]) -> list[MenuItem]:
        """
        Filter menu items based on user permissions.


        :param menu_items: list of all menu items
        """
        items = filter(
            lambda item: self.security_manager.has_access(ACTION_CAN_ACCESS_MENU, item.name), menu_items
        )
        accessible_items = []
        for menu_item in items:
            menu_item_copy = MenuItem(
                **{
                    **menu_item.__dict__,
                    "childs": [],
                }
            )
            if menu_item.childs:
                accessible_children = []
                for child in menu_item.childs:
                    if self.security_manager.has_access(ACTION_CAN_ACCESS_MENU, child.name):
                        accessible_children.append(child)
                menu_item_copy.childs = accessible_children
            accessible_items.append(menu_item_copy)
        return accessible_items

The reason being that this menu list is called in the navbar_menu.html

Enabling these changes further requires changes in the security_manager.py. Is this the correct approach? I did attempt to implement these but that just lead to the need for more changes.

Also, I think that the version checking condition in the override.py can now be removed if it had been implemented solely due to the GET request at /logout endpoint.

From the screencast I see that you have not properly compiled www-assets before running the UI. This has side effects of missing scripts.

What I do not understand is the fix you are attempting to contribute. There IS already a logout menu entry behind the profile:

Why do you plan to add another in this PR?

@jscheffl @shahar1 my sincere apologies for this mishap. I have compiled the www-assets (sorry for this mistake). In my previous comment under the issue, I had presumed that the person who opened the issue tried to go to the /logout/ endpoint in the browser to logout. I should have asked them how exactly was the error occurring. The only instance of 405 error I got was when I tried to enter the /logout/ in the browser. Hence my assumption.

Again, my apologies for this bad PR. I will make a comment under the issue to understand how to recreate the error. Should I close my PR until then?

@jscheffl @shahar1 my sincere apologies for this mishap. I have compiled the www-assets (sorry for this mistake). In my previous comment under the issue, I had presumed that the person who opened the issue tried to go to the /logout/ endpoint in the browser to logout. I should have asked them how exactly was the error occurring. The only instance of 405 error I got was when I tried to enter the /logout/ in the browser. Hence my assumption.

Again, my apologies for this bad PR. I will make a comment under the issue to understand how to recreate the error. Should I close my PR until then?

Try to take it easy. Nothing bad happened :)
You could close this PR for now - try to figure out if you can reproduce the issue. If you can, you may create a new PR to fix it - otherwise, there's plenty of other issues that you could tackle.