remove the setenv.sh from the java role

[alxgomz]

Bug description

This task can only be picked up after the issues bellow have been fixed:

• free the activemq role from using the setenv.sh file #439
• free the sync role from using the setenv.sh file #440
• free the sfs role from using the setenv.sh file #441
• free the trouter role from using the setenv.sh file #442
• free the transformers role from using the setenv.sh file #443
• free the search role from using the setenv.sh file #444
• free the tomcatrole from using the setenv.sh file #445
• free the repository role from using the setenv.sh file #446

The file setenv.sh is deployed by the java role using template and amended using its dependent roles. such as tomcat, search, sync, etc…

This is problematic generally speaking (in particular for idempotence) as we want to avoid cases where one part of the playbook may interfere with what another part needs to do.

Target OS

all

Ansible error

molecule idempotence test failures (currently skipped using molecule-idempotence-notest)

Acceptance criteria

• java do not provide a setenv.sh file
• tests are amended accordingly