Added a tool server that exposes all tools as endpoints

[whitead]

This adds a new method - make_tool_server - that will create an authenticated server that has all environment tools exposed as endpoints.

This is used in a new entry point:

aviary tools [env name]

which will then start a server and host the tools:

[jamesbraza]

Is this used at all?

And if it's used, do you mind documenting where the current state gets housed (e.g. is it JSON in the content)?

[whitead]

This is related to tree search - I had to promote this code to prevent dependence on aviary-internal

[whitead]

So, I think when @sidnarayanan promotes the rest of his code it will be documented then.

[jamesbraza]

Fwiw, tree search is not going to be in aviary, it will be in LDP. Should we put it in LDP with tree search?

I guess I think it's confusing to have this message subclass here without usage or docs, and no specialized behaviors

[sidnarayanan]

EnvStateMessage should be in aviary - it can be used by environments to indicate that a particular message in the returned observation represents the state of the env. I don't see any harm in keeping it here.

[whitead]

We'll have to work this out in another PR - basically @sidnarayanan needs this message type in cloning, cloning should not depend on ldp or aviary-internal.

[jamesbraza]

Can we at least put Sid's comment into the docstring for EnvStateMessage then?

[whitead]

Beyond "A message that contains the current state of the environment." ?

[jamesbraza]

How about something like this:

Suggested change

	class EnvStateMessage(Message):
	"""A message that contains the current state of the environment."""
	class EnvStateMessage(Message):
	"""
	A message variant whose contents are known to contain the environment state.
	For example, the contents can be a JSON serialization of the environment state.
	"""

[jamesbraza]

Suggested change

	"""Add two numbers."""
	"""Add two numbers.""" # Allows testing empty descriptions