Use 1es releasejob for deployments

[hallipr]

• Only use deployment: step for package deployment job
  • deployment steps should not clone the repo or download resources other than build artifacts
• Stage the credscan suppression file with the build artifact instead of downloading from github

[scbedd]

I'm a little bit weirded out by the output artifacts used here, as historically I believe they were added to reduce the amount of generated YML. We should try a build of storage or comunication release (just up to triggering the release) to ensure that we don't hit max yml size without having this output inlined in the templatecontext.

[hallipr]

The output artifacts allow you to compress your injected SDL steps by combining all of the scans across all of your outputs. This is in contract to inline output tasks like 1ES.PublishNuget or 1ES.PublishArtifact that will inject all of the sdl steps per inlined task.

[hallipr]

The amount of YML doesn't really change. We were declaring 2 job outputs per artifact, and now we're declaring 2 publish tasks per artifact.