Migrate to BOPTEST-Service as only deployment architecture

[dhblum]

This issue will migrate BOPTEST-Service to be used as the only deployment architecture and RESTful API. The primary advantage and reason for this is to alleviate the need to maintain the two closely matched but not exact RESTful APIs, alleviate developers and users having to develop and maintain interfaces for each of them, and generally streamline the implementation of new BOPTEST features which are also supported by BOPTEST-Service. A downside is that the service architecture is more complex for those who use BOPTEST locally. However, with continued usage of docker-compose, users will still be able to deploy BOPTEST easily and in the same basic way.

Todos:

• Migrate BOPTEST-Service code (Service v0.4.0, BOPTEST v0.6.0)
• Fix 400 error response message in Service when wrong point name - see For the service implementation, invalid input names to advance do not return 400 as expected. #671.
• Fix Julia example controller variable error, silence docker build
• Pass all BOPTEST unit tests
• Remove javascript example
• Migrate Service-specific unit tests
• Update release notes
• Update README, including README example commands and unit test (if still needed)
• Incorporate lessons-learned from ADRENALIN (logging and timeouts) - see Migrate logging and timeout changes from NREL/boptest-service #684.
• Update get_html_IO, find_days, create_ttl to work with Service architecture (see also Update utility scripts to work with Service architecture and add unit tests to utility scripts #700)

[dhblum]

@kbenne FYI I've created this issue.

[dhblum]

Closed by #652.