* Content Service changes both ACS-1781 and 1782
* Ignore test temporarily
* ACS-1782 fix test
* ACS-1782 Test and service updates
* ACS-1781 Tests for Content Service and Store
* ACS-1782 disable rest api DAU
* Discovery API DAU Unit Tests - Asserts
* Discovery API DAU Unit Tests
* Discovery API DAU Unit Test Class
* Discovery API DAU
* ACS-1789 DiscoveryApi DAU
* Discovery API DAU Unit Tests Renamed Methods
* Integration Test Assert
* Unit Test Imports Removal
* Copyright Dates Updated
* Copyright Dates Updated
Co-authored-by: Sara Aspery <sara.aspery@alfresco.com>
* Content Service changes both ACS-1781 and 1782
* Ignore test temporarily
* ACS-1782 fix test
* ACS-1782 Test and service updates
* ACS-1781 Tests for Content Service and Store
* ACS-1782 disable rest api DAU
* ACS-1782 fix mocks in unit test
* ACS-1782 Fix integration test
* ACS-1781 Config set up and validation
* ACS-1781 Unit tests for config validation
* ACS-1865 Code tidy up
* ACS-1865 Updates from PR review
* ACS-1865 Updates from review
* Added validation to the ScriptActionExecuter class to enforce the existing constraints on parameter script-ref (Repo has the constraint to only allow scripts in Data Dictionary / Scripts and AGS has the constraint to only allow scripts in Data Dictionary / Records Management / Records Management Scripts") by validating if the given scriptRef is in the allowed valued of the constraint set on that param
* Added a new unit test for AGS to make sure that rmscript action still works as expected when the script is in the correct folder and fails when not
* Added new case in ActionServiceImpl2Test#testExecuteScript to assert that the transaction fails when we execute the action with an invalid script
* Moved test testActionResult from ActionServiceImplTest to class ActionServiceImpl2Test - Before it ran with a script not in Data Dictionary so with the added validation it started to fail. I moved the unit test do avoid duplicating the code to create the script in the correct location.
