un-escape html strings

[andrewstillv15]

Resolves #

Problem

Found via terraform, some fields return unescaped strings, causing issues with terraform state as the returned state was different than what was sent & what was in the plan

EX:

╷│ Error: Provider produced inconsistent result after apply││ When applying changes to opslevel_service.eam_automation_adapter_eai, provider “provider[\“[registry.terraform.io/opslevel/opslevel](http://registry.terraform.io/opslevel/opslevel)[\](http://registry.terraform.io/opslevel/opslevel%5C)”]” produced an│ unexpected new value: .description: was cty.StringVal(“Receives the event message from SQS and processes it to create respective Work Groups/IT &│ Functional role resources in EAM.“), but now cty.StringVal(“Receives the event message from SQS and processes it to create respective Work Groups/IT│ & Functional role resources in EAM.“).││ This is a bug in the provider, which should be reported in the provider’s own issue tracker.

Slack thread: https://jk-labs.slack.com/archives/C01G8VB8ZCY/p1767985278906609?thread_ts=1765902727.089339&cid=C01G8VB8ZCY

Solution

Checklist

• I have run this code, and it appears to resolve the stated issue.
• This PR does not reduce total test coverage
• This PR has no user interface changes or has already received approval from product management to change the interface.
• Does this change require a Terraform schema change?
  • If so what is the ticket or PR #
• Make a changie entry that explains the customer facing outcome of this change

[derek-etherton-opslevel]

Makes sense to me, surprised it hasn't come up before

[andrewstillv15]

Makes sense to me, surprised it hasn't come up before

@derek-etherton-opslevel It actually has! There's a commit from 2022 referencing this issue 021611c