fix(ci): also install obp-parent POM to local Maven repo on test shards

When Maven reads the installed obp-commons POM to resolve its transitive
deps, it fetches obp-commons' <parent> declaration (com.tesobe:obp-parent
:1.10.1). That POM is also local-only and not in any remote repo.
Install it first via install:install-file before installing obp-commons.

Author: constantine2nd

.github/workflows/build_container.yml

@@ -164,12 +164,23 @@ jobs:
         with:
           name: compiled-output
 
-      - name: Install obp-commons into local Maven repo
+      - name: Install local artifacts into Maven repo
         run: |
-          # obp-commons is a local multi-module dep not published to any public
-          # repo. The compile job installs it to its own ~/.m2 but that runner
-          # is gone. Re-install from the downloaded artifact so surefire:test
-          # can resolve com.tesobe:obp-commons without hitting remote repos.
+          # The compile runner's ~/.m2 is discarded after that job completes.
+          # Install the two local multi-module artifacts so scalatest:test can
+          # resolve com.tesobe:* without hitting remote repos.
+          #
+          # 1. Parent POM — obp-commons' pom.xml declares obp-parent as its
+          #    <parent>; Maven fetches it when reading transitive deps.
+          mvn install:install-file \
+            -Dfile=pom.xml \
+            -DgroupId=com.tesobe \
+            -DartifactId=obp-parent \
+            -Dversion=1.10.1 \
+            -Dpackaging=pom \
+            -DgeneratePom=false
+          # 2. obp-commons JAR with its full POM (lists compile deps inherited
+          #    by obp-api at test classpath resolution time).
           mvn install:install-file \
             -Dfile=obp-commons/target/obp-commons-1.10.1.jar \
             -DpomFile=obp-commons/pom.xml

.github/workflows/build_pull_request.yml

@@ -164,12 +164,23 @@ jobs:
         with:
           name: compiled-output
 
-      - name: Install obp-commons into local Maven repo
+      - name: Install local artifacts into Maven repo
         run: |
-          # obp-commons is a local multi-module dep not published to any public
-          # repo. The compile job installs it to its own ~/.m2 but that runner
-          # is gone. Re-install from the downloaded artifact so surefire:test
-          # can resolve com.tesobe:obp-commons without hitting remote repos.
+          # The compile runner's ~/.m2 is discarded after that job completes.
+          # Install the two local multi-module artifacts so scalatest:test can
+          # resolve com.tesobe:* without hitting remote repos.
+          #
+          # 1. Parent POM — obp-commons' pom.xml declares obp-parent as its
+          #    <parent>; Maven fetches it when reading transitive deps.
+          mvn install:install-file \
+            -Dfile=pom.xml \
+            -DgroupId=com.tesobe \
+            -DartifactId=obp-parent \
+            -Dversion=1.10.1 \
+            -Dpackaging=pom \
+            -DgeneratePom=false
+          # 2. obp-commons JAR with its full POM (lists compile deps inherited
+          #    by obp-api at test classpath resolution time).
           mvn install:install-file \
             -Dfile=obp-commons/target/obp-commons-1.10.1.jar \
             -DpomFile=obp-commons/pom.xml