This PR addresses 2 issues:

• node v20 based actions are deprecated and will be disabled in June 2026

  • this action uses checkout@v4 and setup-java@v4
  • they are both candidates for deprecation
  • wherever possible the most current versions have been used instead

• Users couldn't specify a specific SQLcl version to be installed

  • Oracle SQLcl projects workflow is based on a specific SQLcl release
  • if the SQLcl runtime doesn't match the one specified in .dbtools/project.config.json a deployment will fail
  • it is important that users can specify a matching SQLcl version to ensure consistent deployments
  • the logic employed in the action now matches that found in homebrew

Smaller changes include an updated readme and the addition of a couple extra tests to ensure both the latest SQLcl can be deployed as well as a specific version