chore: move 3rd party notices to post-pipeline

[Cerchie]

Summary of Changes

one of the low-hanging fruits listed here #247

wasn't sure whether to add it as a job under the main task or as a separate task... thoughtS?

Pull request checklist

Please check if your PR fulfills the following (if applicable):

• Tests:
  • Added new
  • Updated existing
  • Deleted existing
• Have you validated this change locally against a running instance of the Quarkus dev server?

  make quarkus-dev

• Have you validated this change against a locally running native executable?

  make mvn-package-native && ./target/ide-sidecar-*-runner

[Cerchie]

note: working on this ci failure:

Unprocessable YAML file.
Error: [{"Schema does not allow additional properties.", "#/after_pipeline/task/jobs/1/dependencies"}, {"Schema does not allow additional properties.", "#/after_pipeline/task/jobs/1/prologue"}, {"Schema does not allow additional properties.", "#/after_pipeline/task/jobs/1/run"}]

[Cerchie]

closing to read up on semaphore CI

[rohitsanj]

1. Create a new pipeline file update-third-party-notices.yml
2. Add commands to main job in the pipeline file update-third-party-notices.yml
3. Add an auto promotion to main semaphore.yml file called "Update third party notices" with when condition as when: "branch =~ '.*' and change_in(['/pom.xml', '/NOTICE.txt'], {default_branch: 'main', branch_range: '$SEMAPHORE_GIT_COMMIT_RANGE', pipeline_file: 'ignore'})"