Dependency Update Checker Workflow

[mbien]

Maven dependency update hint analog, but for binaries-list files and put into a workflow. I used the util already for PRs like #6918 and thought this would have greater value when run by CI so others can use it too.

output looks like:

/home/runner/work/netbeans/netbeans/ide/libs.graalsdk/external/binaries-list
    org.graalvm.sdk:graal-sdk                          20.3.0 -> 23.1.1
    org.graalvm.sdk:launcher-common                    20.3.0 -> 23.1.1
...

see job summary or log for full output:
https://github.com/apache/netbeans/actions/runs/7442427492

workflow is currently configured to run only on manual dispatch (this will only work once merged to master). This means that it can be manually triggered from https://github.com/apache/netbeans/actions/workflows/dependency-checks.yml

btw: the very first version of this util generated temporary pom files for each module containing binaries-list and then ran mvn verify versions:display-dependency-updates, this is the more direct approach without extra steps which download half of the internet.

[lkishalmi]

Looks good. The only thing, that instead of throwing a RuntimeException on errors, I'd just log a one liner, so the process would continue, instead of failing fast.

[mbien]

@lkishalmi my thought was that someone who is running the script via actions or locally, would probably restart it anyway if there are networking issues. If this happens to be a problem, we could add a retry loop there and then fail after 3 retries or so.

It is manually triggered, it won't run automatically in PRs or so that is why I think fail-fast is better there.