Core: Translations: extend config/option flow base strings

[balloob]

The problem

We don't cover yet all common base strings. We should introduce more:

• two factor authentication strings
• The fields pin, name, api_token

Here's the relevant docs section:
https://developers.home-assistant.io/docs/internationalization/core#introducing-new-strings

Related tasks:

• [ ] Use as many references as possible, including in options flow translations

Split out of #34264

Environment

• Home Assistant Core release with the issue: 112
• Last working Home Assistant Core release (if known):
• Operating environment (OS/Container/Supervised/Core):
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

[djpremier]

Suggestion unavailable_account, unavailable_service and unavailable_device

[SNoof85]

Forgot to reference to this issue in that already merged PR : #40963

[SNoof85]

https://github.com/search?q=reauth_successful+repo%3Ahome-assistant%2Fcore+filename%3Astrings.json&type=Code&ref=advsearch&l=&l=

Proposal for new common string : "reauth_successful": "Re-authentication was successful"

[balloob]

Sounds good. Want to make a PR for that?

[SNoof85]

Yes, will do :) => Done ! #41316

[SNoof85]

https://github.com/search?q=not_internet_accessible+repo%3Ahome-assistant%2Fcore+filename%3Astrings.json&type=Code&ref=advsearch&l=&l=
Would it be OK to create one for this too ?
"not_internet_accessible": "Your Home Assistant instance needs to be accessible from the internet"
Do we need to handle the integration/service name in the error message ?

[bieniu]

Proposal for new common string : "invalid_host": "Invalid hostname or IP address"

https://github.com/search?q=invalid_host+repo%3Ahome-assistant%2Fcore+filename%3Astrings.json&type=Code&ref=advsearch&l=&l=