Df 269 add df classification validation

[Cap-n-Cook]

Overview

Added df-classification support. Changes needed to be made in a few unexpected places, namely the OpaClient and the Argument class in order to support classification structure used by df-classification.

More likely than not, more work needs to be done to fully support df-classification classifications, but this will be handled in a separate PR.

I removed any methods that IntelliJ highlighted as "safe delete," meaning they weren't being used for the sake of readability. I also removed commented out code blocks for the same reason.

Another major change is the classification validation no longer checks if a classification is supported by the deployment. This is handled by df-classification, which uses the cluster classification level defined in .Values.global.classification to determine if a classification is valid for the system.

Related Issues

Part of DATAFABRIC-269

Test Procedure

1. Bring up a cluster with the df-269-add-df-classification-to-arcadedb branch in data fabric
2. clone the df-269-add-security-marking-validation branch of df-classification & run make kind
3. clone the df-269-add-security-marking-validation branch of df-arcadedb & run make kind
4. change the images of the df-arcadedb pod to use the dev tag for arcadedb and classification containers
5. login to keycloak and remove the user from the data stewards group
6. in the arcade UI, to run this query (this should fail):

INSERT INTO People CONTENT
{
  firstName: 'Enzo2',
  lastName: 'Ferrari',
  classification:{
  	components: {
    	classification: ['SECRET'],
        disseminationControls: ['REL'],
        releasableTo: ['USA', 'FVEY'],
        ownerProducer: ['USA']
    },
    attributes:{
    	firstName: 'U',
        lastName: 'U'
    }
  }
 }

7. For the above query to save, you have to change the user's clearance_usa attribute to S AND you'll have to update the CLASSIFICATION_LEVEL on the df-classification pod to SECRET. To do this, navigate to the raft-arcadedb deployment.yaml and replace the .Values.global.classification with SECRET. Once this is done, redeploy the pod using
   dfdev cluster deploy -x raft-arcadedb.
8. Re-run the above query and confirm that the document is accepted.

[Cap-n-Cook]

Converted this to a draft so I can resolve conflicts. Dev has new keycloak attributes changes.