[adwk67]

Part of stackabletech/docker-images#1647.

This PR contains changes to make the hbase-opa-authorizer compatible with HBase 3.0.0. In summary:

• unit tests now use juniper rather than junit
• function signatures etc. have been changed to be inline with 3.0.0
• docs have been updated to give the correct scope
• built with JDK 17 instead of 11
• tests have been updated with the correct fixtures and coverage/non-coverage test updated to confirm that all expected callouts have been implemented (with comments for those that are not)

Tested with a build from stackabletech/docker-images#1678 and tests from stackabletech/hbase-operator#815:

--- PASS: kuttl (703.81s)                                                                                                                                                                                   
      --- PASS: kuttl/harness (0.00s)                                                                                                                                                                         
          --- PASS: kuttl/harness/opa_hbase-opa-2.6.6_hdfs-latest-3.5.0_zookeeper-latest-3.9.6_krb5-1.21.1_opa-latest-1.16.2_openshift-false (703.80s)                                                        
  PASS

--- PASS: kuttl (389.54s)                                                                                                                                                                                   
      --- PASS: kuttl/harness (0.00s)                                                                                                                                                                         
          --- PASS: kuttl/harness/opa_hbase-opa-3.0.0_hdfs-latest-3.5.0_zookeeper-latest-3.9.6_krb5-1.21.1_opa-latest-1.16.2_openshift-false (389.53s)                                                        
  PASS 

Important

This PR will be tagged with release-1.0.0, meaning that we cannot continue to develop release 0.3.0 (used for HBase 2.6.6) in the main branch. There are two options for any subsequent changes to 0.3.0:

• impelment them as patches in docker-images (patch folders are currently empty as there is no upstream external project from which delta patches are to be derived from)
• create a release-0.3.0 branch int his repo and make changes there

Unit-Test results:

[INFO] Tests run: 100, Failures: 0, Errors: 0, Skipped: 2
...
[INFO] --- exec:3.1.0:exec (opa-policy-test) @ hbase-opa-authorizer ---
src/test/rego/hbase_test.rego:14:
data.hbase_test.test_all_denied_inputs: PASS (27.466652ms)

  denied fixtures: 22

src/test/rego/hbase_test.rego:6:
data.hbase_test.test_all_allowed_inputs: PASS (27.474756ms)

  allowed fixtures: 19
--------------------------------------------------------------------------------
PASS: 2/2
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:40 min
[INFO] Finished at: 2026-10-05T13:23:19Z
[INFO] ------------------------------------------------------------------------

[NickLarsenNZ]

LGTM

[NickLarsenNZ]

This PR will be tagged with release-1.0.0, meaning that we cannot continue to develop release 0.3.0 (used for HBase 2.6.6) in the main branch. There are two options for any subsequent changes to 0.3.0:

* impelment them as patches in docker-images (patch folders are currently empty as there is no upstream external project from which delta patches are to be derived from)

* create a release-0.3.0 branch int his repo and make changes there

I think we can just create a branch for it if/when needed.