chore: refactor proto, schema, and jobservice for multiRM

[carolinaecalderon]

Description

Make changes to api calls to include ResourceManager field for requests that call implemented agentRM/kubernetesRM ResourceManager methods.
Bubble up these changes to the jobservice & ResourceManager interface.

Test Plan

Pass existing tests.

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

Ticket

RM-43

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	13be116
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/65de150c052f5700082f7258
😎 Deploy Preview	https://deploy-preview-8875--determined-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Attention: Patch coverage is 39.24051% with 192 lines in your changes are missing coverage. Please review.

Project coverage is 47.55%. Comparing base (c029327) to head (13be116).
Report is 14 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #8875    +/-   ##
========================================
  Coverage   47.54%   47.55%            
========================================
  Files        1065     1065            
  Lines      170218   170421   +203     
  Branches     2241     2241            
========================================
+ Hits        80937    81041   +104     
- Misses      89123    89222    +99     
  Partials      158      158            

Flag	Coverage Δ
backend	43.34% <15.58%> (-0.01%)	⬇️
harness	63.74% <25.60%> (-0.07%)	⬇️
web	42.56% <57.96%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
master/internal/command/command.go	67.96% <100.00%> (+0.13%)	⬆️
master/internal/rm/agentrm/resource_pool.go	25.16% <ø> (ø)
master/internal/rm/kubernetesrm/resource_pool.go	0.00% <ø> (ø)
master/pkg/model/experiment_config.go	39.24% <ø> (ø)
master/pkg/schemas/expconf/experiment_config.go	64.21% <ø> (ø)
master/pkg/schemas/zgen_schemas.go	1.24% <ø> (ø)
master/internal/api_experiment.go	54.84% <0.00%> (ø)
master/internal/api_job.go	0.00% <0.00%> (ø)
master/internal/experiment_job_service.go	0.00% <0.00%> (ø)
master/pkg/tasks/task_generic.go	55.31% <0.00%> (ø)
... and 9 more

... and 4 files with indirect coverage changes

[rb-determined-ai]

maybe this is a dumb question... but why do users need to specify the resource manager and the resource pool?

Why don't we just use resource pools and they specify those? This is a layer of hierarchy that has never made sense to me.

[carolinaecalderon]

Ah this is for use in the multi-RM project -- multiple resource managers can have resource pools with the same name. In that case, we need to use the resource manager name to qualify & identify it.

[rb-determined-ai]

why don't we just disallow multiple resource pools with the same name?

[rb-determined-ai]

I hear the answer to this is "because slurm".

Gross, but ok.

[stoksc]

FWIW @rb-determined-ai , the way we're approaching this is users will only need to specify if there is a conflict, still. Otherwise no one knows this param exists.