Rename adapter -> controller

[jamienoss]

Resolves #25

• Renames all instances of adapter -> controller and similar.
• Renames all instances of react -> control and similar
• Last commit adds a few layers/hooks for easier customization of the control execution without needing to always customize the core control func/algorithm. This should facilitate in easier sharing of control code.

I had thought about adding context manager funcs, but it didn't quite make sense for this. The only example I could think of is when running multiple controls, i.e., when doing one thing, you then want to do another, but 🤷 .

with thermostat:
  monitor_results()

#or 
with thermostat:
  do_other_stuff_requiring_constant_temp()

However, the above examples require concurrency...

[amitschang]

couple comments inline

[amitschang]

I know this was already in place and was confusing before, but since this is more generic than controller (it is used for controller and hardware), maybe should be DriverDescriptor, or PluginDescriptor or something. If we don't change here I can make an issue to track that.

[jamienoss]

@amitschang I think this would be better if just nuked and replaced with evolver.base.BaseConfig, sound good to you?

[jamienoss]

I won't change in this PR though, there's a much-needed refactor to incorporate the construction pattern from #37 and this can get addressed then.

[amitschang]

could you add a test or two for this, especially the return mutation to be sure we capture the desired mechanism?

[jamienoss]

Wasn't really sure what you were expecting here but I at least added some very rudimentary tests for you.