update config generator for translator proxy and jdc

[lucasbalieiro]

closes #174.

this patch ended up being slightly more complex than initially expected because we need to support multiple versions of sv2-apps. Until this point, we had not encountered any breaking changes in the configuration file format.

the approach taken in this PR is intentionally minimal: introduce version-aware branching logic in the configuration generator and place the user_identity field in the location expected by each supported version.

specifically:

• For sv2-apps v0.3.5, user_identity is written at the top level of the configuration.
• For the current main branch, user_identity is written under the upstream section.

This ensures compatibility with both versions while keeping the change set small and focused on resolving the immediate issue.

ps: I would recommend revisiting this implementation in the future. As we begin supporting additional versions of sv2-apps, the current branching approach may become increasingly difficult to maintain. A more structured versioning strategy for configuration generation would likely be beneficial in the long term. For now, however, this solution provides a practical fix for the main branch and unblocks affected users.

[GitGab19]

ps: I would recommend revisiting this implementation in the future. As we begin supporting additional versions of sv2-apps, the current branching approach may become increasingly difficult to maintain. A more structured versioning strategy for configuration generation would likely be beneficial in the long term. For now, however, this solution provides a practical fix for the main branch and unblocks affected users.

The good thing is that after the work on bitcoin_core_sv2 defined here, we won't need to handle different apps' versions anymore.

So when those changes land on sv2-apps, we can finally remove all this branching logic which we introduced up to now.

[Shourya742]

tested it locally seems to work fine.

tACK

[GitGab19]

The good thing is that after the work on bitcoin_core_sv2 defined stratum-mining/sv2-apps#516, we won't need to handle different apps' versions anymore.

So when those changes land on sv2-apps, we can finally remove all this branching logic which we introduced up to now.

Opened this issue to better track it: #176

[GitGab19]

tACK (both v30.2 and v31)