feat: #811 Add tracebility comments in Effective Set

[KamalArya]

Pull Request

Summary

To make it clear where each parameter in the Effective Set comes from, comments should be added next to every value showing its source.

Issue

Fixes #811

Breaking Change?

• Yes
• No

If yes, describe the breaking change and its impact (e.g., API changes, behavior changes, or required updates for users).

Scope / Project

effective set

Implementation Notes

This change is aimed at adding traceability support in the effective set:
Issue: #811
Documentation: https://github.com/Netcracker/qubership-envgene/blob/main/docs/features/calculator-cli.md#version-20-traceability-comments
Approach:

The Parameter object passed during YAML dumping is unwrapped, and origin details are added as comments based on conditions.

Implemented custom representer for Parameter class.

Tests / Evidence

Describe how the changes were verified, including:

• Tests added or updated (e.g., unit, integration, end-to-end)
• Manual testing steps or results
• Screenshots, logs, or other evidence (if applicable)

Additional Notes

As comments are added to generated credentials.yaml file as well inside effective set, the comment were getting encrypted during SOPS encryption.

Applied fix: switch effective-set credential files only to --encrypted-regex='.*'.
Concretely, surgical change in sops_handler.py and the pre-commit crypt.py:

function get_sops_scope_flag(file_path):
if file_path matches "/effective-set/<...>/credentials.ya?ml"
and filename != "external-credentials.ya?ml":
scope = '--encrypted-regex "."'
else:
scope = '--unencrypted-regex "^type$"' # current behavior, unchanged

function encrypt(file_path, age_public_key):
scope_flag = get_sops_scope_flag(file_path)
run: sops --encrypt --age <age_public_key> <scope_flag> <file_path>

There are changes in internal envgene repository as well