fix: API ML services log cleanup

[hrishikesh-nalawade]

Description

Zowe logs were being populated with repeated “URL/Path not transformed” entries, as shown below. The proposed changes will ensure that such logs generated for API ML services are excluded.

ZWEAC705W The home page url for service CACHINGSERVICE was not transformed. Not able to select route for url https://***:7555/cachingservice of the service cachingservice. Original url used.
ZWEAC708E The API base path for service CACHINGSERVICE was not retrieved. Not able to select API base path for the service cachingservice. Original url used.
ZWEAC705W The home page url for service ZAAS was not transformed. Not able to select route for url https://***:7558/ of the service zaas. Original url used.
ZWEAC708E The API base path for service ZAAS was not retrieved. Not able to select API base path for the service zaas. Original url used.
ZWEAC705W The home page url for service CACHINGSERVICE was not transformed. Not able to select route for url https://***:7555/cachingservice of the service cachingservice. Original url used.
ZWEAC708E The API base path for service CACHINGSERVICE was not retrieved. Not able to select API base path for the service cachingservice. Original url used.
ZWEAC705W The home page url for service DISCOVERY was not transformed. Not able to select route for url https://***:7553/ of the service discovery. Original url used.
ZWEAC708E The API base path for service DISCOVERY was not retrieved. Not able to select API base path for the service discovery. Original url used. 

Linked to #4088

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

[sonarqubecloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud