As a QE, I want to be able to test the partner contract creation logic without injecting messages onto UMB. 

There are three ways that logic can be invoked in swatch.  Rest API, kafka messages, or UMB messages.  Today, IQE supports Rest API & Kafka, but not UMB.  swatch-contracts consumes UMB messages from entitlement gateway.  We don't want to have to inject UMB messages for testing purposes in a stage/prod environment, so we want to provide a different interface.

Note: this is a blocker for automation testing to be written for several cards as part of the SaaS contracts epic.  See https://docs.google.com/document/d/17OlJcxuIwbQ_BaUSzCO3uAPxSSPZlVVvNTB27fQZuO0/edit#heading=h.ho8xbhdacbah([https://docs.google.com/document/d/17OlJcxuIwbQ_BaUSzCO3uAPxSSPZlVVvNTB27fQZuO0/edit#heading=h.ho8xbhdacbah] "Follow link")  This card is for a quick fix for unblocking contract testing.  A more long-term pattern/solution TBD as part of SWATCH-1160

Done:

• Internal API created in the swatch-contract service that takes a jstring representing PartnerEntitlementContract and invokes the consumeContract 
  https://github.com/RedHatInsights/rhsm-subscriptions/blob/3b362798feb3db093c0f317ba21a2a88bd9f5117/swatch-contracts/src/main/java/com/redhat/swatch/contract/resource/ContractUMBMessageConsumer.java#L59
• should be defined in openapi spec
• rpc-style

• Internal API needs to be secured by the usual means and tagged as a test API
• The API should be blocked from usage in prod
• QE should write a wrapper for this in SMQE tools
•