Model-Loader service of A&AI has it's Log Provider Configuration File sealed inside the WAR

The A&AI "model-loader" service has its logging provider configuration file inside its WAR. This does not support logging provider configuration as described in ONAP application logging guidelines (https://wiki.onap.org/download/attachments/1015849/ONAP%20application%20logging%20guidelines.pdf?api=v2), which state that "[a]n application should provide the ability to change the logging level [...] with no/minimum impact to the running application" and that "[a] configuration file should be used by logging application to determine the actual directory specification where to write the log file", and is not consistent with standardized configuration locations suggested by the ONAP Logging Enhancements project (https://wiki.onap.org/display/DW/Logging+Enhancements+Project+Proposal#LoggingEnhancementsProjectProposal-Defaultproviderconfigurationlocations).

A&AI uses Logback as its logging framework. The "logback.xml" configuration file is in "/opt/jetty/jetty*/webapps/model-loader/WEB-INF/classes/". It should be inside the "config" folder.

Fix suggested is as below:

1. Create the directory /etc/onap/aai/conf.d/model-loader/
2. Move "logback.xml" file from "/opt/jetty/jetty*/webapps/model-loader/WEB-INF/classes/" to folder created in Step 1.