Handle the case when the connection name is not known before wallet download

[jhorvath]

In case the connection name is not known before the DB Wallet is downloaded, parse wallet's tnsnames.ora and take one from there.

[mbien]

hmm. why can't the secondary jobs find the artifact in this PR. This never happened during testing.

looking at the first workflow run:
https://github.com/apache/netbeans/runs/5769887724?check_suite_focus=true

1. base job uploaded successfully
2. secondary jobs could download, however, the file was corrupted and extraction failed
3. all secondary jobs failed, but the cleanup job removed the artifact successfully

All subsequent workflow runs fail with secondary jobs not finding any artifacts, despite the primary job getting a success msg after upload:
"Artifact build has been successfully uploaded!"

i have never seen something like that. might be a temp gh issue?

[mbien]

@jhorvath i deleted the complete workflow run. Could you do me a favor and force push into this PR to trigger a fresh run?

[jhorvath]

@mbien It is pushed already, but just 3 checks are queued.

[mbien]

It is pushed already, but just 3 checks are queued.

@jhorvath it works like a pipeline now. Two primary jobs build, rest starts later after they succeed and use the artifact of the primary build for tests.

the summary shows a nice graph https://github.com/apache/netbeans/actions/runs/2071857027

anyway. Everything appears to be working fine now. This might just have been a weird anomaly. At least we know how to fix it if it happens again.