fix: change tab name in login page and clean up keycloak folder

Dockerfile

@@ -45,7 +45,7 @@ COPY nginx/ ./
 RUN chmod +x /app/run.sh
 
 COPY --from=ci /app/build build
-COPY otomi.jar /app/
+COPY /console-keycloak/APL.jar /app/
 
 RUN chown -R app:app /app
 

otomi-keycloak/META-INF/keycloak-themes.json → console-keycloak/APL/META-INF/keycloak-themes.json

@@ -1,7 +1,7 @@
 {
   "themes": [
     {
-      "name": "otomi",
+      "name": "APL",
       "types": ["login"]
     }
   ]

console-keycloak/APL/theme/APL/login/messages/messages_en.properties

@@ -0,0 +1 @@
+loginTitle=Sign in to APL console

otomi-keycloak/README.md → console-keycloak/README.md

@@ -1,25 +1,24 @@
 # Local development
 
-Run keycloak locally with `otomi` theme mounted.
+Run keycloak locally with `APL` theme mounted.
 
 ```
-docker run -p 8084:8080 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=admin -v $PWD/keycloak/themes/otomi:/opt/keycloak/themes/otomi -v $PWD/keycloak/providers:/opt/keycloak/providers keycloak/keycloak start-dev
+docker run -p 8084:8080 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=admin -v $PWD/keycloak/themes/APL:/opt/keycloak/themes/APL console -v $PWD/keycloak/providers:/opt/keycloak/providers keycloak/keycloak start-dev
 ```
 
 Next:
 
 - go to http://localhost:8084/admin/master/console/#/master/realm-settings/themes and login with default credentials,
-- set login theme to `otomi`,
-- logout from keycloak in order to see login page with `otomi` theme,
+- set login theme to `APL`,
+- logout from keycloak in order to see login page with `APL` theme,
 - modify code on this directory and observe changes after web page reload.
 
 # Deploying new theme
 
-- navigate to otomi-console/otomi-keycloak/theme
+- navigate to apl-console/console-keycloak
 - make sure java and the full JDK are installed on the machine
-- run command `jar cf otomi.jar -C otomi `
+- run command `jar cf APL.jar -C APL `
 - This will create a jar file in the child resources folder
-- move this file to the otomi-console root directory, overriding the old otomi.jar
 - the jar file will be consumed in the build step, so there is no manual deploy step
 
 # References