Support {{...}} double curly brace based as alternate placeholder delimiter alongside ${...}

[authorjapps]

Add {{...}} placeholder resolution with identical feature parity to existing ${...}, without changing current ${...} behavior. Both style must work.

Description

Zerocode currently resolves ${...} placeholders in JSON/YAML test steps, target-env property files, and CSV-parameterized steps (via TokenUtils, ZeroCodeAssertionsProcessorImpl, ZeroCodeParameterizedProcessorImpl, and ApplicationMainModule). Users should be able to use {{...}} as an alternative for all the same token types (SYSTEM.PROPERTY:, SYSTEM.ENV:, RANDOM., PARAM., host property keys, etc.), with both delimiters usable side by side, and ${...} continuing to work exactly as before.

Acceptance Criteria

• All existing ${...} placeholder with all features (system property/env var tokens, random tokens, masked tokens, host property-file key resolution, CSV PARAM tokens, target-env file placeholder resolution) work identically when written as {{...}}.
• Existing ${...} test suites and fixtures pass unmodified (no regression), and a mixed file using both ${...} and {{...}} in the same test step resolves correctly.
• Unrelated pre-existing {{...}} usage (WireMock Handlebars templates, e.g. {{localdatetime offset='...'}}) remains untouched/literal since those tokens don't resolve against any known token or property key. (Note: Wiremock integration should be removed in a separate PR -- raise a separate ticket to remove Wiremock integration)

So during the development of this ticket, if Wiremock conflicts(it should not), then remove Wiremock dependencies 1st via a PR(with a notice in README file), then develop this ticket.

Wiremock removal issue is here: #783

[maria-surugiu]

Hi @authorjapps! I'd like to work on this task.

[authorjapps]

Hi @authorjapps! I'd like to work on this task.

Thanks, Go ahead please. Will assign this to you shortly

[authorjapps]

Hi @authorjapps! I'd like to work on this task.

Issue assigned.

@maria-surugiu , Can you put a high level plan(not too much detailed I mean) here, to implement this before actually you implement it and raise a PR ?

[maria-surugiu]

Hi @authorjapps! I'd like to work on this task.

Issue assigned.

@maria-surugiu , Can you put a high level plan(not too much detailed I mean) here, to implement this before actually you implement it and raise a PR ?

Thanks for assigning me!

Here is the plan:

• Setup: clone, build, run existing tests + familiarize myself with the project.
• Check Wiremock dependencies and remove them if they conflict, as requested.
• Identify the existing logic for ${...} and introduce similar logic for {{...}}.
• Run (and add) tests to see if both {{...}} and ${...} work without breaking existing functionalities.
• Update the README or other documentation if necessary.

Let me know what you think and if you need more info.