add refresh token phase to AuthorizationCode scenario

[ddurham2]

refresh token load test scenario

resolves #416

[kami619]

@ddurham2 I am currently testing this locally, do you think anything else is left on this PR before we can take this forward and move it from Draft status to Ready for review ? Also made some minor changes to make the code little bit more explicit.

[ddurham2]

Yes, I'm still tweaking it locally. I'm both doing tests and adjusting KC and adjusting the tests as I go. I did get it up to 100k on a local minikube deployment. I still need to figure out how to specify some of the testing parameters which are new for this test, I think.
I'll try and commit some things shortly.

[ddurham2]

I saw the gatling java process up in the 3.5GB range when ramping up to 100k users

[kami619]

@ahus1 - I did the test with both minikube and openshift and also with the ec2 load runners and local benchmark, things looked good to me. do you want to give this a last look, before I merge it ?

[ahus1]

Thank you @ddurham2 for contributing this change and @kami619 for reviewing it thoroughly!

I added one tiny bit in f0d86cb I remember from a previous life, that one using shared connections, it used to make sense to increase he maxConnectionsPerHost.

I'm now merging this.

[ddurham2]

Thanks guys. Much appreciated!