Add integration tests for LoLa/mw::com feature in ITF

[Subramanian-K812]

Add communication (LoLa / mw::com) integration tests to ITF

Summary

Adds an ITF test suite for the communication module (LoLa / mw::com).

The suite drives its own two-process scenario —
showcases/standalone/comm_fit: fit_sender + fit_receiver, built on the
same public com_api Rust crate com-api-example uses — as two real OS
processes communicating over real shared memory.

The tests assert on data the consumer actually observes — delivery, ordering,
and value-integrity of a sequence number the sender encodes in the payload —
rather than on log strings the application prints about its own
configuration, so a regression in the middleware is what breaks them.

The suite runs under the existing //feature_integration_tests/itf:itf
target on both the Linux (Docker) and QNX (QEMU) configs.

What's added

File	Purpose
showcases/standalone/comm_fit/fit_sender.rs	Producer: offers the VehicleInterface service instance, publishes left_tire samples carrying a monotonically increasing sequence number.
showcases/standalone/comm_fit/fit_receiver.rs	Consumer: discovers the service (with retry, so start order doesn't matter), subscribes, and prints one line per received sample for the ITF to assert on.
showcases/standalone/comm_fit/BUILD	Builds fit_sender/fit_receiver and bundles them for deployment.
showcases/BUILD	Deploys the comm_fit bundle into the reference image alongside com-api-example.
patches/communication/002-expose-com-api-gen.patch	Exposes com-api-gen (the generated VehicleInterface) outside //score/mw/com, so fit_sender/fit_receiver can depend on it.
bazel_common/score_modules_target_sw.MODULE.bazel	Adds the patch above to the score_communication git_override.
known_good.json	Same patch entry, kept aligned with the generated MODULE.bazel (required by the known_good_correct CI check).
feature_integration_tests/itf/test_communication.py	The test cases (see coverage table below).
feature_integration_tests/itf/comm_helpers.py	Exchange helpers and output oracles (CommResult, ordering/integrity checks, deployment-config and ASIL-B ACL scenario helpers).
feature_integration_tests/itf/test_properties.py	Fallback-safe wrapper around attribute_plugin.add_test_properties, mirroring feature_integration_tests/test_cases/test_properties.py (verified identical).
feature_integration_tests/itf/BUILD	Adds the new sources to the itf target and activates the requirement-traceability plugin (-p attribute_plugin + @score_tooling//python_basics/score_pytest:attribute_plugin dep).

Test coverage

Test	Verifies (requirement IDs)	Oracle
test_fit_binaries_are_deployed	— (deployment smoke check)	fit_sender/fit_receiver binaries present on the target image.
test_event_exchange_delivers_data	event_type, producer_consumer, interfaces, data_driven_arch, service_discovery	Consumer discovers the service (as a separate OS process from the producer), receives samples, exits cleanly.
test_received_samples_are_ordered_and_intact	data_corruption, data_reordering	Received sequence numbers are non-decreasing and every value is one the sender actually sent (never a garbled value).
test_deployment_config_is_read_from_runtime_path	depl_config_runtime	SHM binding / service identity are read at runtime from an explicit -s <path> manifest, not compiled in.
test_late_joining_consumer_receives_data	stateless_communication, producer_consumer	A consumer subscribing 3s after the producer started still binds and receives valid samples from the SHM ring buffer.
test_missing_config_file_fails_deterministically	depl_config_runtime	Missing manifest → deterministic failure bounded by a shell timeout, never reaches service discovery.
test_truncated_config_fails_deterministically	depl_config_runtime	Syntactically invalid JSON → same deterministic-failure contract (observed: process aborts, RECV_EXIT=134).
test_schema_invalid_config_fails_deterministically	depl_config_runtime	Well-formed JSON missing the required schema structure → same contract.
test_mixed_criticality_acl_isolation	asil, acl_for_consumer, acl_for_producer, acl_per_service_instance	ASIL-B provider offers to one allowed UID; a concurrently-running excluded UID is denied and cannot affect the allowed consumer's stream. (Runs on Linux; skipped on QNX — see Limitations.)

Requirement IDs are the published feat_req__com__* identifiers, attached via
@add_test_properties(partially_verifies=[...]) so they are emitted into the
JUnit XML <properties> — the same traceability convention used by the
persistency FIT cases under feature_integration_tests/test_cases.

The negative-config tests (missing/truncated/schema_invalid) and the ACL
isolation test each run against a dedicated instance specifier that no other
test offers, so they cannot observe another test's leftover shared-memory
state (the QEMU target is session-scoped and persists across the whole test
file, unlike the Docker plugin's fresh-container-per-test model).

Limitations

• ASIL-B ACL isolation on QNX. allowedConsumer enforcement is a
  shared-memory ACL keyed on the consumer's real UID, so exercising it needs a
  consumer running under a UID excluded from the allow-list (setpriv on
  Linux, on -u <uid> on QNX). On QNX, LoLa's MessagePassingService
  endpoint registration itself requires privilege, so a consumer launched
  under a lower-privilege UID aborts at message-passing setup before
  reaching the shared-memory ACL check. The denial therefore cannot be
  attributed to the ACL on QNX, so the test skips there; it runs on Linux,
  where an unprivileged UID can still bring up its endpoint and so reaches the
  ACL check the assertions rely on.

Verification

• QNX 8.0 under QEMU (--config=qnx-x86_64): confirmed 8 passed, 1
  skipped across multiple runs (test_mixed_criticality_acl_isolation
  skips for the reason under Limitations).
• Linux under Docker (--config=linux-x86_64, what CI's "Linux — Build &
  Integration Test" job runs): confirmed 9 passed
• Requirement-traceability properties confirmed present in the generated
  JUnit XML (bazel-testlogs/.../itf/test.xml)