Add new resource hints: max active bundles per worker

[AMOOOMA]

Adding SDK support for passing in max active bundles per worker as new resource hints.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @jrmccluskey for label python.
R: @shunping for label java.
R: @lostluck for label go.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[lostluck]

The Go changes LGTM, though I must remind that WRT the model, hints are only intended for performance, not correctness. That is, Ressource hints that a runner doesn't know, must be able to be ignored for correctness.

For this one, I'd be most worried about trying to force single threading for such a bundle communicating to a GPU. On the other hand "Please run as many of these as the worker can handle eg. 100" would be very safe. Really depends on the intent. I got lost about what the name of the hint was and over speculated. This is at least precise in the intent despite the concern I have above.

[shunping]

The Java code change looks good. Just one minor comment.

[jrmccluskey]

Python piece LGTM

[shunping]

Thanks! Looks good to me as well.