[Chaos Test] Actor instantiation burst

Some applications might create many actors in a small amount of time. This burst will be simulated by creating actors of a random type and activating it at a fixed rate of X tps for a durantion D at an interval. The flooded actor type must be different than the actor type used in the app but it should also be registered by Hashtag Actor Service to make sure that service gets traffic load. Some slowness is expected in the data processing but recovered after burst is over.

Parents: dapr/test-infra#11 dapr/test-infra#22

The issue names no files, tests, or entry points, so first locate the existing chaos-test and actor-registration infrastructure. Clarify the values for X, D, and the interval, then verify the burst uses a different actor type registered with Hashtag Actor Service and that processing recovers afterward.

Written by the indexing model from the issue text.