Add Maven Central Repository to pom file for all Service Repos using Github Actions.

[kaladay]

Without Maven Central Repository added, builds under Github Actions sometimes fail due to incorrectly attempting to get Projects from the TAMU file repositories instead of the appropriate ones. Adding Maven Central Repository should resolve this issue.

The problem appears to be network/github related, but this is unclear.
It seems that github, sometimes inconsistently fails to fetch files from maven centrals default repository.
By adding the mirror, an alternative repository is used in addition to maven central.
Failures are inconsistent and do not happen everytime, for example:

• https://github.com/TAMULib/CatalogService/runs/1737625414?check_suite_focus=true (pgjdbc-versions-1.1.2.pom)
• https://github.com/TAMULib/CatalogService/runs/1737625567?check_suite_focus=true

The first fails and the second passes, despite being the same commits.
The package that fails is coincidental and will be different from time to time.
(For example here tomcat-embed-websocket-8.5.43.pom fails: https://github.com/TAMULib/CAP/runs/1728569099#step:8:6762 )

Adding what is essentially a second maven central repository to search for the files through adds robustness via the redundancy and helps reduce problems with githubs potential networking issues. For example, central represents the default maven repository and mvnrepository represents the added additional maven repository.
In CAP, this commit is fetching the file from central https://github.com/TAMULib/CAP/runs/1728973172?check_suite_focus=true#step:8:3033 but for a different file it fetches from mvnrepository https://github.com/TAMULib/CAP/runs/1728973172?check_suite_focus=true#step:8:3036 (after trying both tamu-releases and tamu-snapshots for the package spring-boot-dependencies-1.5.22.RELEASE.pom). It seems that for some reason it failed to fetch spring-boot-dependencies-1.5.22.RELEASE.pom from central and then attempts to fetch from the tamu repositories and finally the mvnrepository.

This essentially makes the mvnrepository a failsafe to use in the event central fails and the files are not on tamu-release and not on tamu-snapshots.

https://github.com/TAMULib/CAP/runs/1728973172?check_suite_focus=true#step:8:3033

See also:

• https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-dependencies/1.5.22.RELEASE/spring-boot-dependencies-1.5.22.RELEASE.pom
• https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-dependencies/1.5.22.RELEASE/spring-boot-dependencies-1.5.22.RELEASE.pom
• https://repo1.maven.org/maven2/org/springframework/spring-context/4.3.25.RELEASE/spring-context-4.3.25.RELEASE.pom
• https://repo.maven.apache.org/maven2/org/springframework/spring-context/4.3.25.RELEASE/spring-context-4.3.25.RELEASE.pom
• https://repo.maven.apache.org/maven2/org/postgresql/pgjdbc-versions/1.1.2/pgjdbc-versions-1.1.2.pom
• https://repo1.maven.org/maven2/org/postgresql/pgjdbc-versions/1.1.2/pgjdbc-versions-1.1.2.pom

The following need to be updated:

• SAGE
• CAP
• LibraryServiceStatusSystemService
• MetadataAssignmentToolService
• GIFMButtonService
• ProjectManagementService
• CatalogService
• The Private Repositories