Draft: Feature/tmf702

Closes #51

Implemented TMF702 API in accordance with the previously implemented TMF APIs.

As discussed in OSL's meetings, to provide a separation of concerns between this API and the TMF639. The Apache Camel routes related to Resource creation and update were commented on the TMF639, So that the Resource creation (namely in CRIDGE) is made through the TMF702.

Test Coverage