feat: Run SAST and DAST Aviator audits separately in SSC CI action

[jmadhur87]

• SSC ci action now has separate Aviator audits for SAST and DAST

  • SAST: DO_AVIATOR_SAST_AUDIT
  • DAST: DO_AVIATOR_DAST_AUDIT

• DAST audit now waits for the scan results to be in SSC before it starts:

  • wait for DAST scan to be published (DAST_PUBLISH_WAIT)
  • find the published DAST artifacts (DAST_ARTIFACTS)
  • wait for them to finish processing (DAST_ARTIFACTS_WAIT)

• DAST_PUBLISH runs sc-dast scan publish only when the scan has
  "submit for audit" turned off. Auto-published scans are handled too.

• DAST_WAIT runs automatically when the DAST audit is enabled, so there is no
  need to also set DO_DAST_WAIT.

• Warning is logged if the scan settings point to a different app version
  than the CI app version.

• Remediations stay SAST only (AVIATOR_REMEDIATIONS), as DAST has no remediations.

• AVIATOR_SAST_WAIT now runs after the DAST audit, so SSC can process the
  SAST audit result while the DAST steps run.

• New option fcli sc-dast scan wait-for --published: waits until the scan
  results are published to SSC, not only until the scan is complete.