Refactor check env and fossa cli

[elaguerta-nr]

Refactor check-env and FOSSA CLI

Refactor all workflows to pull out duplicate code from check_env and fossa jobs. Fix bugs that suppressed errors from FOSSA analyze, and incorrectly set the fossaAnalyzeResult custom property.

Refactors

• Pull out FOSSA CLI duplicated code into a composite action at .github/composite/fossa-composite/action.yml.
  • A composite action enables the FOSSA steps to be called in the same job as the calling job. This allows the FOSSA CLI to to run after required configuration steps such as installing package managers.
• Pull out check-env duplicated code into a reusable workflow at .github/workflows/fossa-check-env.yml
  • A reusable workflow runs as a separate job. This allows it to be tracked and monitored separately from the FOSSA job. It also minimizes passing of required secrets from the caller to the check-env job.

Bugfixes

• Change error checking of fossa CLI commands to search for [ERROR] in error logs (exact match)
  • previous check was incorrectly matching on an informational log with the word "error"
  • We are resorting to text matching because we couldn't find an exit code for fossa analyze that indicates an execution error. Failing error codes indicate a policy violation, which we don't want to block on at this time.
• Initialize HAS_FOSSA_TARGETS and FOSSA_ANALYZE_RESULT env variables to ""
  • This ensures that the values of custom properties get set to default values if the FOSSA job encounters errors.
• fossa-elixir.yml
  • passelixir-version input variable
  • fix "ANALZYE" typo that suppressed fossa analyze errors (by replacing all FOSSA work with call to shared composite workflow)
• fossa-ruby.yml
  • fix the same ANALZYE typo
• fossa-scala.yml
  • fix the same ANALZYE typo

[lucasgonze]

No issues jump out at me.