Added path based system functionality from radar-output-restructure

[this-Aditya]

Added Functionalities from Radar-Output for Consistent Path-Based Structure

This functionality has not been extracted from radar-output-restructure and moved to radar-commons because some differences arise when using radar-gateway. Hence, these functionalities are added separately to radar-gateway with slight modifications, as listed below:

Modifications:

• Key-Value Handling:
  The radar-output-restructure uses the key and value parameters as a generic record, but this approach has not been adopted for radar-gateway.

  For example, consider the send method from the phone audio input plugin in radar-commons-android.
  It sends the Kafka topic’s key-value pair separately from the audio file. Hence, key and value path-formatted plugins have been removed.

• Path Formatter Extensions Handling:
  The extensions in radar-output are not part of PathFormatterParameters, and they need to be supplied to FormattedPathFactory::init as a parameter or otherwise to PathConfig::createFactory.
  This approach is not suitable for radar-gateway because, for every request, all components for path formatting get regenerated, and previous objects are discarded if the extension is explicitly passed every time.

  To simplify this, the extension configuration has been moved to PathFormatParameter and this can be passed for every request with recreating objects

• File Naming Consistency:
  Every file field will have a random UUID appended as a suffix to maintain consistency with the current file upload approach.

• Removal of the Attempts Field:
  The attempts field has been removed as it is not currently used in radar-gateway.

• Some other minor changes.