Improve Ocean class tests

[mariacarmina]

Fixes #158 .

Changes proposed in this PR:

• added getter methods where needed
• fix unit tests for Ocean class

[paulo-ocean]

overall , LGTM. i don´t have any issues with having extra getters here and there :-) but i think that we should think about removing these individual tests (including unit:storage), its getting too big and we can always run the command manually,
That said, i think these tests are pretty much useless to be honest :-)
If we want to keep them its ok, but they are not really testing anything;
We create one config object, pass it in the constructor to a bunch of different objects and then check if the properties match?? But of course they match, its the same object...
It like adding 1 + 1 and checking if its 2 :-)
I'm not saying they are wrong, but i don't see any added value

[mariacarmina]

overall , LGTM. i don´t have any issues with having extra getters here and there :-) but i think that we should think about removing these individual tests (including unit:storage), its getting too big and we can always run the command manually, That said, i think these tests are pretty much useless to be honest :-) If we want to keep them its ok, but they are not really testing anything; We create one config object, pass it in the constructor to a bunch of different objects and then check if the properties match?? But of course they match, its the same object... It like adding 1 + 1 and checking if its 2 :-) I'm not saying they are wrong, but i don't see any added value

I can remove the scripts for package.json, because I understood the reason to not populate useless with scripts and I'll remove them. For testing I wanted to test that the components were initialized correctly (and wanted to access some fields). The issue mentioned that we should have individual/granular test for OceanIndexer, OceanP2P and OceanProvider. If you have any suggestions regarding the assert statements, I am happy to add those.
Thank you @paulo-ocean for review!