use dockerised and dedicated ontologies_api instance for unit testing

[alexskr]

Currently, we are using production Bioportal api for unit testing of ontologies_api_ruby_client which limits the kind of unit tests we can safely run. Instead of this we should spin up a dockerized and dedicated ontologies_api for unit testing.

[alexskr]

unit tests expect to have a few things already to be present on the API side, things like BRO ontology, category, at lest two ontology starting with letter 'c' so my question is should we pre-create those before unit tests kick off or perhaps have ruby_client create them as a part of the unit test run?

[syphax-bouazzouni]

I think that ruby_client will create them before the corresponding test as needed. Like what was done in the backend tests, e.g https://github.com/ncbo/ontologies_linked_data/blob/master/test/util/test_notifications.rb#L8-L10

And an empty dockerized ontologies_api would be also easier and faster to use in future UI tests.