Remove deprecated remote classes

[balloob]

Description:

This removes the deprecated remote classes. The helper methods to call the API are still in place.

• Removed remote.HomeAssistant, remote.EventBus, remote.StateMachine, connect_remote_events, disconnect_remote_events and the API /api/event_forwarding

Checklist:

If the code does not interact with devices:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• Tests have been added to verify that the new code works.

[mention-bot]

@balloob, thanks for your PR! By analyzing the history of the files in this pull request, we identified @fabaff, @rmkraus and @philipbl to be potential reviewers.

[AddoSolutions]

This breaks quite a few docs, a few notables ones are:

https://home-assistant.io/developers/python_api/
https://home-assistant.io/developers/multiple_instances/

Not sure how to do remote instances now, any suggestions?

Originally it was said to run it the following way in a slave.py file:

import homeassistant.remote as remote
import homeassistant.bootstrap as bootstrap

# Location of the Master API: host, password, port.
# Password and port are optional.
remote_api = remote.API("127.0.0.1", "password", 8124)

# Initialize slave
hass = remote.HomeAssistant(remote_api)

# To add an interface to the slave on localhost:8123
bootstrap.setup_component(hass, 'frontend')

hass.start()
hass.block_till_stopped()

[cmsimike]

@AddoSolutions
I don't think remote instances work anymore. I tried to have a similar setup but with the removal of remote.HomeAssistant(...), the only option we have left is the MQTT Event Stream but that doesn't do what I want (it only pushes events from one hass to another, it doesn't allow me to talk about entities in one hass instance from another).

I was actually just talking in the gitter chat about this.

[balloob]

I have updated the docs to mark or remove the parts that are no longer available.

This remote connection was very unstable and at some point broken with no developer fixing it and taking ownership. A future implementation should not be part of the main repo but should come as it's own package.