Change github action input map handling

[de-jcup]

Situation

In our integration tests for the SecHub github action, we use currently a field mockedInputMap:

sechub/github-actions/scan/__test__/integrationtest.test.ts

Lines 86 to 96 in 987f2a5

	function initInputMap() {
	mockedInputMap.clear();
	mockedInputMap.set(input.PARAM_SECHUB_SERVER_URL, `https://localhost:${integrationTestContext.serverPort}`);
	mockedInputMap.set(input.PARAM_SECHUB_USER, `${integrationTestContext.serverUserId}`);
	mockedInputMap.set(input.PARAM_API_TOKEN, `${integrationTestContext.serverApiToken}`);
	mockedInputMap.set(input.PARAM_CLIENT_VERSION, 'latest');
	mockedInputMap.set(input.PARAM_ADD_SCM_HISTORY, 'false');
	mockedInputMap.set(input.PARAM_REPORT_FORMATS, 'json');
	mockedInputMap.set(input.PARAM_TRUST_ALL, 'true'); // self signed certificate in test...
	mockedInputMap.set(input.PARAM_FAIL_JOB_ON_FINDING, 'true');
	}

Each integrtion test calls this method!

When the integration tests would run parallel, the initialization could bring up flaky tests because the commonly used mockedInputMap could bring up race conditions...

Currently the integration test setup in package.json calls
jest --runInBand --testPathPattern='integrationtest.test.ts'

reading https://archive.jestjs.io/docs/en/24.x/cli#--runinband :

Run all tests serially in the current process

But if somebody runs the tests not with the --runInBand option, the test will become flaky!

Wanted

Even without --runInBand the tests shall be not flaky

Solution

• change function initInputMap() to return a new created map
• drop the field of the map
• introduce an inputMapResolver , write tests...
• change launcher to use a inputMapResolver
• change mocking for integration test, use mock for inputMapResolver as parameter for launch...
• adopt change also to https://github.com/mercedes-benz/sechub/blob/develop/github-actions/scan/src/main.ts
  use there a real inputMapResolver which resolves data from github core...