Add support for high number of compositions

It has been created a new performance test for jmeter to generate thousands of compositions and instances.
The following issues has been reported after the Investigation of the behavior of ACM-runtime and participant simulator:

the GET actions of Api ACM-runtime do not have paginations, in particular the following endpoints:
- GET /onap/policy/clamp/acm/v2/compositions
- GET /onap/policy/clamp/acm/v2/compositions/{compositionId}/instances
- GET /onap/policy/clamp/acm/v2/participants
The monitoring should not scan all compositions and instances, but only compositions and instances that are in transitional state.
Restart scenario has not been tested yet

Page and size of the pagination

it needs to define the default max page "paginationDefaultSize" that will be used by AC-runtime and it could insert into the parameters file:

runtime:
..........
..........
  acmParameters:
    paginationDefaultSize: 10
    toscaElementName: org.onap.policy.clamp.acm.AutomationCompositionElement
    toscaCompositionName: org.onap.policy.clamp.acm.AutomationComposition

Assuming that paginationDefaultSize = 10, the page and size of the pagination will be defined as the example below:

endpoint	page	size

endpoint	page	size
GET /onap/policy/clamp/acm/v2/compositions	0	10
GET /onap/policy/clamp/acm/v2/compositions?page=1&size=5	1	5
GET /onap/policy/clamp/acm/v2/compositions?page=2	2	10
GET /onap/policy/clamp/acm/v2/compositions?size=20	0	20

Restart scenario

Not tested yet, but it should be slow-down the participants. Maybe a database support could fix it.