Add login_method config option to fix login issue with RouterOS Version > 6.43

[Bouni]

Description:

Mikrotik changed the used login method with version 6.43 of their RouterOS and disabled the old token login method with version 6.45.1. Therefore the mikrotik component was no longer able to login and use the API.

Related issue: fixes #25189

Pull request with documentation for home-assistant.io : home-assistant/home-assistant.io#9877

Example entry for configuration.yaml (if applicable):

- platform: mikrotik
  host: 192.168.23.1
  track_new_devices: false
  login_method: plain
  username: !secret mikrotik_username
  password: !secret mikrotik_password

Checklist:

• [ x ] The code change is tested and works locally.
• [ x ] Local tests pass with tox. Your PR cannot be merged unless tests pass
• [ x ] There is no commented out code in this PR.
• [ x ] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• [ x ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• [ x ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[MartinHjelmare]

Is this a breaking change? Does the user need to do anything?

[Bouni]

@MartinHjelmare
Indeed as I think of it, but I could just extend the login_methods tuple so that it has both login methods and therefore it would continue for all users without the need to change anything

[MartinHjelmare]

If we can solve it nicely without requiring user interaction, that would be the best.

[Bouni]

@MartinHjelmare Just pushed a commit in which I changed the login method tuple so that users don't have to take action. If they want to avoid the log message on their router, they still can set the login_method in the config and specify which method to use.

[MartinHjelmare]

What is the log message that can be avoided?

[Bouni]

Its login failure for user homeassistant from 192.168.23.104 via api
The reason is that you pass a tuple with both login methods to the connect method.
If you put the token method first, users with Version < 6.45.1 will not get an error, but users with versions >= 6.45.1 will do.
On the other hand if we swap the order of login methods, users with Versions < 6.43 will get the error but all others not.
In my opinion its better the we it is in my last commit becuase users will eventually get to versions > 6.43
which will automatically result in no errors.

[MartinHjelmare]

Sounds good. Let's make sure we explain clearly in the docs how the user can avoid the log message by configuration.