Added separate executor list to handle CDS unauthenticated endpoints

[aka4rKO]

Added separate executor list to handle CDS unauthenticated endpoints

$subject by not engaging the MTLS executor for the following unauthenticated elected resources:
"/banking/products", "/banking/products/{productId}", "/discovery/status", "/discovery/outages"

Issue link:

• https://github.com/wso2-enterprise/wso2-ob-internal/issues/855

Doc Issue: Optional, link issue from documentation repository

Applicable Labels: OB 3.0.0, CDS Toolkit

---

Development Checklist

1. Built complete solution with pull request in place.
2. Ran checkstyle plugin with pull request in place.
3. Ran Findbugs plugin with pull request in place.
4. Ran FindSecurityBugs plugin and verified report.
5. Formatted code according to WSO2 code style.
6. Have you verify the PR does't commit any keys, passwords, tokens, usernames, or other secrets?
7. Migration scripts written (if applicable).
8. Have you followed secure coding standards in WSO2 Secure Engineering Guidelines?

Testing Checklist

1. Written unit tests.
2. Documented test scenarios(link available in guides).
3. Written automation tests (link available in guides).
4. Verified tests in multiple database environments (if applicable).
5. Verified tests in multiple deployed specifications (if applicable).
6. Tested with OBBI enabled (if applicable).
7. Tested with specification regulatory conformance suites (if applicable).

Resources

Knowledge Base: https://sites.google.com/wso2.com/open-banking/

Guides: https://sites.google.com/wso2.com/open-banking/developer-guides

[imesh94]

Shall we change the logic of detecting Common endpoints along with this?

[aka4rKO]

Shall we change the logic of detecting Common endpoints along with this?

@imesh94 done with c334acc