Create GitHub Action(s) to process a PR of an NR1 Application

[tangollama]

On the initiation of a Pull Request:

• (if possible) Identify the submodule referenced in the PR (assuming one submodule change per PR)
• Checkout / update the submodule
• Build the application
• Lint-check the code
• Validate the structure as an application Create / config an Action that validates the expected structure of an NR1 application #3
• N/A - See Comment Lookup a uuid in a repo-traceable local data store that maps this submodule to the global catalog account. If none exists, generate one and save the uuid. If it exists, use that value to perform the next step. See Create a repo-based data store for mapping account id's to submodule names #6.
• N/A - See Comment Validate the ability to publish the code Create / config an Action that builds the NR1 package validates the ability to publish it to NR1 #2
• Validate the ability to publish the catalog data Create / config an Action that validates that a submodule contains the Catalog components #1
• Execute a security and licensing check using Synk

[jbeveland27]

These 2 steps are not going to be accomplished on pull_request.

Would need access to commit missing/incorrect uuid to the forked repo for this to work. Instead, this will only be done when PR is approved and merged.

• Lookup a uuid in a repo-traceable local data store that maps this submodule to the global catalog account. If none exists, generate one and save the uuid. If it exists, use that value to perform the next step. See Create a repo-based data store for mapping account id's to submodule names #6.

There's no secure method for passing needed API keys to a forked repo (#8).

• Validate the ability to publish the code Create / config an Action that builds the NR1 package validates the ability to publish it to NR1 #2

[jbeveland27]

The catalog-pr Workflow now meets these requirements. Closing issue.