Add async_add_executor_job function to improve performance and avoid cpython bug about architecture

[balloob]

So I just added a PR that introduces hass.async_add_executor_job. This function could probably replace like 80% of all calls to async_add_job. One thing that I like about this is that it will make it clear where we are using the executor.

[balloob]

We can't add a parameter to the function to make it choose something.. what you're proposing is a new function.

We were talking about that the other day with @andrey-git. I'm on my phone so don't know the pr anymore but we had list to split it up

[balloob]

Found the comment. home-assistant/core#14429 (comment)

As initial plans were already laid out in that comment, I don't mind if we add a new function async_add_executor_job that behaves similar to async_add_job for threaded functions.

[pvizeli]

My problem with split the code is, that's never possible to cleanup the old code. At the end we mess the code base with a new function for maybe 400ms per 1milion requests.

I think we shold focus for a clean code base (core) they work as simple as possible. For Typing. We use python and that give this project the magic while we can do stuff that are not possible in other language. For runtime, typing make no change in python and that mean it's not usable.

[pvizeli]

Yeah I'm fine with this function but I say only that it's never been possible to cleanup the code base and we need maintain this two function with same functionality until the end of home-assistant asyncio usage :)