[TR] Enable V2X communication in Smart Intersection serving as TR for Smart Corridor

[ajagadi1]

Description

This draft PR introduces V2X publish in Smart Intersection so that it serves as TR for Smart Corridor.

1. Note: Change the webUI port from 443:443 to 8443:443 in docker-compose file to avoid clashing with V2XHUB. Make appropriate nginx.conf changes. (Ensure to open scenescape UI in 8443 port, ex: https://IP:8443
2. Build scenescape-v2x-bridge image (docker build -t scenescape-v2x-bridge) by following instructions in https://github.com/open-edge-platform/scenescape/tree/main/tools/v2x and define it in compose file. For actual usage in the release ready app, scenescape can be cloned as submodule and scenescape-v2x-bridge image can be built as a part of setup.
3. Start the app (The scope of TR is docker compose only, no helm chart). Smart Intersection UI will be accessible on https://host-ip:8443, https://host-ip:8443/grafana/ etc.,
4. Note that port mapping of 1883 done in MQTT broker in order for debugging purposes only. This helps launch mqtt-explorer GUI and check all scenescape messages. Open mqtt-explorer and change host to localhost. Keep encryption on and connect to view messages.

5. Create a 'logs' directory inside 'V2X-Hub/configuration' and Install V2XHUB by running initialization.sh: https://github.com/usdot-fhwa-OPS/V2X-Hub/tree/develop/configuration . Change the IP address in the V2XHUB UI from localhost to your host-ip. Update the Pedestrian plugin configuration. Set DataProvider as REST and Set the WebServiceIP to your host-ip and enable pedestrial plugin. Details see: https://github.com/open-edge-platform/scenescape/tree/main/tools/v2x. The amount of accepted J2735 messages in V2XHUB can be seen in Messages section of the UI.:

Fixes # (issue)
https://jira.devtools.intel.com/browse/ITEP-84130

How Has This Been Tested?

Manual testing

Checklist:

• I agree to use the APACHE-2.0 license for my code changes.
• I have not introduced any 3rd party components incompatible with APACHE-2.0.
• I have not included any company confidential information, trade secret, password or security token.
• I have performed a self-review of my code.