[loadgenerator] added loadgeneratorFloodHomepage flagd

[bornav]

Changes

Added a loadgeneratorFloodHomepage flagd that when enabled floods the homepage with a large amount of traffic
Depending on the typical load of the sample, the load generation can be overwritten by changing the flagd variant number in the demo.flagd.json

Merge Requirements

For new features contributions please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs
• Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: bornav (8a3bbfd, cf72b62, 7126e96)

[mviitane]

I tried to run this PR just before the latest commit one hour ago and got it running, but now, for some reason it fails to checkout this branch. For the other PRs this is working:

$ gh pr checkout 1481
From github.com:open-telemetry/opentelemetry-demo
 * branch            refs/pull/1481/head -> FETCH_HEAD
Already up to date.

$ gh pr checkout 1486
From github.com:open-telemetry/opentelemetry-demo
 ! [rejected]        refs/pull/1486/head -> Load-generator-Web-request-spamming  (non-fast-forward)
failed to run git: exit status 1

$ gh pr checkout 1489
M	src/otelcollector/otelcol-config-extras.yml
Switched to branch 'snyk-upgrade-dd6a7df28d38a21b56af93ecc710f974'

[mviitane]

With my first tests, I tried to flood with these settings to go a bit higher:

"variants": {
  "high":  1000,
  "medium": 100,
  "low":     10,
  "off":      0
},
"defaultVariant": "high"

You could provide more options than just 100.

In general, this is a really interesting scenario! With this, one can adjust the load levels outside the LoadGen UI.

[bornav]

I tried to run this PR just before the latest commit one hour ago and got it running, but now, for some reason it fails to checkout this branch. For the other PRs this is working:

$ gh pr checkout 1481
From github.com:open-telemetry/opentelemetry-demo
 * branch            refs/pull/1481/head -> FETCH_HEAD
Already up to date.

$ gh pr checkout 1486
From github.com:open-telemetry/opentelemetry-demo
 ! [rejected]        refs/pull/1486/head -> Load-generator-Web-request-spamming  (non-fast-forward)
failed to run git: exit status 1

$ gh pr checkout 1489
M	src/otelcollector/otelcol-config-extras.yml
Switched to branch 'snyk-upgrade-dd6a7df28d38a21b56af93ecc710f974'

could not replicate the issue from my side

With my first tests, I tried to flood with these settings to go a bit higher:

"variants": {
  "high":  1000,
  "medium": 100,
  "low":     10,
  "off":      0
},
"defaultVariant": "high"

You could provide more options than just 100.

In general, this is a really interesting scenario! With this, one can adjust the load levels outside the LoadGen UI.

purposely left it on a vague number, for a reason, we can't assume the load high will be the same for all environments.
Lets take 1000 as example, for the current env it more than enough, however for some other environment, the value 1000, may be insignificant

but if there is an agreement on the suggestion, I will gladly apply it

[mviitane]

Sorry, it took a while, but I got rid of the problem in my branch by creating a new branch with
gh pr checkout 1486 -b Load-generator-Web-request-spamming-new

But this PR seems good to me.

[julianocosta89]

2 minor adjusts, but looks good to me!

[austinlparker]

The integration test failure doesn't seem related to this PR, so I'll go ahead and merge.