DM-38138: Create a build task for remote submission

[zhaoyuyoung]

Checklist

• ran Jenkins
• added a release note for user-visible changes to doc/changes

[codecov]

Codecov Report

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

Project coverage is 77.86%. Comparing base (8a6235f) to head (83186a3).

Files	Patch %	Lines
python/lsst/ctrl/bps/drivers.py	0.00%	22 Missing ⚠️
python/lsst/ctrl/bps/submit.py	9.09%	10 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #138      +/-   ##
==========================================
- Coverage   78.44%   77.86%   -0.58%     
==========================================
  Files          40       40              
  Lines        3099     3122      +23     
  Branches      529      536       +7     
==========================================
  Hits         2431     2431              
- Misses        578      601      +23     
  Partials       90       90              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[timj]

@MichelleGower Comments? Adding anything to bps that wants to know about a plugin seems wrong.

[MichelleGower]

I haven't had a chance to look at this yet other than this one line. What @timj says is correct. There shouldn't be a need to write WMS specific code inside ctrl_bps. If we're wanting to do all of the bps submission stages remotely or let's make that more generic to inside a compute job (even a local job), then we should change the bps code generically to do this.

[zhaoyuyoung]

Yes I agree. At the time when we worked on the remote submission, it's not a generic operation for other WMS, so we tried to keep other WMS intact but only apply the remote submission to PanDA. Basically we need bps has a way to stop generating quantum graph and execution bulter at the stage of transform when it's a remote submission.