[DT-2983] Make adjustments to template for using methods on getting Java Record values.

[otchet-broad]

Addresses

https://broadworkbench.atlassian.net/browse/DT-2983

Summary

The stack trace values in production logs indicates an issue with obtaining values from Java Records. This seems counter to the Freemarker release notes here: https://freemarker.apache.org/docs/versions_2_3_33.html. These release notes indicate that Java Record values can be obtained as if they were bean values as long as the configuration is updated to point to v_2_3_33 (ours is!).

This PR:

• Updates the Freemarker configuration to v_2_3_34
• Adds parens to darCode accessor so that we don't assume magic in freemarker is working
• Adds a test to verify the darCode value appears in the template output.

---

Have you read CONTRIBUTING.md lately? If not, do that first.

• Label PR with a Jira ticket number and include a link to the ticket
• Label PR with a security risk modifier [no, low, medium, high]
• PR describes scope of changes
• Get a minimum of one thumbs worth of review, preferably two if enough team members are available
• Get PO sign-off for all non-trivial UI or workflow changes
• Verify all tests go green
• Test this change deployed correctly and works on dev environment after deployment

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rushtong]

Nice find 👍🏽

[kevinmarete]

👍🏾

[fboulnois]

Do we need to update any of the other templates?

[otchet-broad]

@fboulnois - This is the only message we send that uses a class that extends Record. Other classes use Java objects that have getters.