Add CI workflows to support tag and branch builds

[Angus-repo]

@MilosKozak
Modify aaps-ci to support building APKs for 3.x versions.

Add branch-ci for testers who need to build the dev branch (this preserves the original aaps-ci behavior).

Upgrade setup-java from v4 to v5.

Important: Because the GitHub Actions UI cannot load options dynamically, whenever a new tag is added or the JVM mapping changes, the following files must be updated manually:
1. aaps-ci: add the latest tag to the dropdown menu

2.	jdk-map.json: add the JDK version mapping for the tag and update the latest version mapping

Changes to GitHub Actions only take effect after they are merged into the default branch (master).

please review

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[MilosKozak]

@Angus-repo
good! but this broke building from branch (ie dev)

[Angus-repo]

@MilosKozak
Because aaps-ci is intended for general users, I kept aaps-ci for public use, while using branch-ci when there is a need to build other branches.
I have also added this explanation to the documentation.

openaps/AndroidAPSdocs/#2557

please review

[MilosKozak]

I don't see branch-ci in workflow ... anything else must be done? merged to master?

[Angus-repo]

@MilosKozak

Because GitHub Actions workflows must be placed in the default branch (master), and master does not currently have branch-ci.yml, branch-ci is not visible.

You can change Settings -> Default branch to the dev branch, and then you will be able to see it.

Or, merge this PR into master, and then branch-ci will also become visible.