Upgrade the pipeline trigger logic to run on updates to previously processed release branches

[chrisammon3000]

Description

The gfe-db update pipeline (AWS Lambda) checks the IMGT repository once a day and triggers a build if a new release has been added. However if additional changes are made to that release they are not picked up. The solution would be to upgrade the logic so that the pipeline also runs when a release branch is updated.

Proposed Solution

In addition to checking for new release branches, the Lambda function should also check for recent commits that include changes to relevant files on the current release branch and rebuild the data so that gfe-db reflects the most current changes. The logic would look something like this:

• State variables:
  • List of releases that have been processed (these are ignored, any release found not on this list is processed and added)
  • List of file assets used for processing (this list never changes)
• Poll the IMGT repository and check for new releases
  • → if a new release is found then trigger a build
  • → or, if a commit has been made to one of the files used for processing on the current or a previously processed release branch then trigger a build

[chrisammon3000]

This feature branch needs to be merged with new commits in the main branch before the pull request can be merged.