Add changes to identify external traffic for infosec data publishing

[imesh94]

Add changes to identify external traffic for infosec data publishing

Due to the multiple redirects happening in the /authorize call and internal traffic to endpoints like /authorize and /token, metrics data becomes inaccurate. This PR contains changes to identify external calls before publishing infosec endpoint data using a header that can be added to the external requests by the load balancer. Repetitive data publishing due to /authorize redirects is also stopped by checking for sessionDataKey query parameter.

Removing APIM side proxies defined for infosec endpoints will be sent in a separate PR.

Issue link: wso2/financial-services-accelerator#157

Doc Issue: Optional, link issue from documentation repository

Applicable Labels: Spec, product, version, type (specify requested labels)

---

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).

Automation Test Details

Test Suite	Test Script IDs
Integration Suite	TCXXXXX, TCXXXX

Conformance Tests Details

Test Suite Name	Test Suite Version	Scenarios	Result
Security Suite	VX.X	Foo, Bar	Passed

Resources

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

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

[nirmal070125]

Is it possible to write a test case to handle the end-to-end scenario by mocking out the components?

[imesh94]

Is it possible to write a test case to handle the end-to-end scenario by mocking out the components?

Added in 81aef69