Add telemetry dataset generator logic

[mithileshreddy04]

Issues Resolved by this Pull Request
Fixes: #4849

Description of the Solution

This PR introduces two major improvements to the telemetry subsystem:

1. Telemetry Dataset Profile Alignment

Updated telemetry dataset profiles to align with specific use cases and removed obsolete configurations:

• Added new profiles: idrac_powerscale, idrac_ldms_powerscale, idrac_ldms, idrac_ome_ufm, idrac_powerscale_vast, ldms_only, powerscale_only, defaults, online_mode, and offline_mode
• Removed obsolete profile: idrac_only (replaced by more specific profiles)
• Renamed profile: idrac_ome_ufm_sfm → idrac_ome_ufm to accurately reflect that SFM is an external integration, not a configurable telemetry_sources entry
• Updated documentation: README files for the generator and datasets reflect these changes

2. Input Validation Log Path Alignment

Moved validate_telemetry_input.log to the project-scoped data path for consistency with Omnia's data management standards:

• New path: <OMNIA_DATA_PATH>/telemetry/log/<OMNIA_PROJECT_NAME>/validate_telemetry_input.log
• Default path: /opt/omnia/telemetry/log/project_default/validate_telemetry_input.log
• Old path: /var/log/omnia/telemetry/validate_telemetry_input.log (no longer updated)
• No changes to other logs: All other telemetry logs (telemetry.log, deploy.log, credentials.log, etc.) remain under /var/log/omnia/telemetry/
• Logging behavior unchanged: Filename, format, and overwrite mode remain the same

The changes ensure:

• Dataset profiles clearly reflect the telemetry sources they enable
• Validation logs are scoped to the project, following the OMNIA_DATA_PATH pattern
• No disruption to existing Ansible logging configurations or other log destinations