Turn openshift-arm profile into general aarch64 (#1995)

* To avoid needing to define the same multiarch container versions for
  bare metal and OpenShift use cases, this commit turns openshift-arm
  into general aarch64 profile.
* Updating the readme file with examples on how to run this profile with
  both OpenShift and bare metal uses.

README.md

@@ -64,6 +64,7 @@ By default, all your tests are running on bare metal (JVM / Dev mode), but you c
 * Redhat-registry: use Redhat docker registry with official supported images instead of community images
 * Serverless: enable Knative or serverless scenarios
 * Operator-scenarios: enable operator scenarios, where the ecosystem of your test is going to be deployed by k8s/OCP operators
+* `aarch64`: profile using versions of containers for test services that work on aarch64
 
 All of these profiles are not mutual exclusive, indeed we encourage you to combine these profiles in order to run complex scenarios.
 
@@ -108,6 +109,16 @@ mvn clean verify -Dall-modules -Dopenshift -pl http/http-minimum
 
 **NOTE:** here we are combining two profiles, profile `openshift` in order to trigger OpenShift execution mode and property `all-modules` to enable `http-modules` profile, where `http/http-minimum` is located.
 
+#### OpenShift & Aarch64
+
+To run test services on OpenShift clusters installed on aarch64, make sure you enable aarch64 profile:
+
+```shell
+mvn clean verify -Dall-modules -Dopenshift -Daarch64 -pl http/http-minimum
+```
+
+**NOTE:** You can comine this with native profile also.
+
 ### OpenShift & Native
 
 Please read [OpenShift](#OpenShift) section first and login into OCP.
@@ -170,6 +181,15 @@ User: `Run http-minimum module.`
 mvn clean verify -Dall-modules -pl http/http-minimum
 ```
 
+#### Bare metal & Aarch64
+
+To run tests on bare metal aarch64, make sure you enable aarch64 profile so that tests are able to launch test service 
+containers:
+
+```shell
+mvn clean verify -Dall-modules -Daarch64 -pl http/http-minimum
+```
+
 #### Bare metal & Native
 
 Same as [OpenShift & Native](#OpenShift--Native) scenarios, Quarkus test framework will reuse the Native binary generated by Maven to run your tests.

pom.xml

@@ -775,24 +775,10 @@
             </build>
         </profile>
         <profile>
-            <!-- You need to be connected to an OpenShift instance to activate this
-                profile! -->
-            <id>openshift-arm</id>
-            <activation>
-                <property>
-                    <name>openshift-arm</name>
-                </property>
-            </activation>
-            <properties>
-                <include.tests>**/*OpenShift*IT.java</include.tests>
-                <exclude.openshift.tests>no</exclude.openshift.tests>
-            </properties>
-        </profile>
-        <profile>
-            <id>openshift-arm-containers</id>
+            <id>aarch64</id>
             <activation>
                 <property>
-                    <name>openshift-arm</name>
+                    <name>aarch64</name>
                 </property>
             </activation>
             <build>
@@ -809,7 +795,6 @@
                                 <configuration>
                                     <systemPropertyVariables>
                                         <!-- always set 'OpenShift' property as that's how detect OpenShift tests inside FW -->
-                                        <openshift>true</openshift>
                                         <ts.arm.missing.services.excludes>true</ts.arm.missing.services.excludes>
                                         <ts.redhat.registry.enabled>true</ts.redhat.registry.enabled>
                                         <!-- Product Services -->