fix: escape commit message and other templated values when building card

[ahanoff]

Problem

opsless/ms-teams-github-actions@2.0.0 crashes with the following error whenever the workflow run's commit message contains a JSON-significant character (e.g. a double quote, backslash, or control character):

Expected ',' or '}' after property value in JSON at position ...

This is not a webhook-uri or token issue. It is a bug in how the action builds the Adaptive Card payload.

Root cause

In src/main.ts:

1. The card template is a JS object that interpolates runtime values via ${$root.*} expressions (e.g. line 58 puts ${$root.commit.message} inside a JSON string field).
2. Line 160 did JSON.stringify(temlpateData) before passing it to new Template(...).
3. The adaptivecards-templating engine substitutes ${...} textually inside that JSON string — it does not JSON-escape the inserted values.
4. Line 199 then did JSON.parse(content) on the result.

So a commit message like build: fix "quoted" task produces:

"value":"[build: fix "quoted" task](https://github.com/org/repo/commit/...)"

which is invalid JSON, and JSON.parse throws. head_commit.message is only trimmed to the first line (line 144), never escaped, so this triggers on every commit title containing ", \, raw tabs, etc. The same latent issue exists for workflow.name.

The duplicate error lines come from core.error(error) followed by core.setFailed(error.message) (lines 245–246).

Fix

Pass the template as a JS object to new Template(...) and use the expanded object directly as the attachment content. Node's JSON.stringify then handles all escaping correctly when serializing webhookBody for the HTTP request.

-  const rawdata = JSON.stringify(temlpateData)
-  const template = new Template(rawdata)
+  const template = new Template(temlpateData)
   const content = template.expand({ $root: { ... } })
   ...
   const webhookBody = {
     type: 'message',
     attachments: [{
       contentType: 'application/vnd.microsoft.card.adaptive',
-      content: JSON.parse(content)
+      content
     }]
   }

This eliminates the stringify → expand → parse round-trip entirely, fixing the issue for all templated values (commit message, workflow name, repository name, etc.), not just commit.message.

Verification

Reproduced the original failure and validated the fix against these commit messages:

• build: fix "quoted" task
• fix: path\with\backslashes
• feat: emoji 🎉 and 'single' quotes
• chore: tabbed\tmessage
• fix: trailing backslash \
• multi-line \n messages (first line kept, per existing behaviour)
• normal ASCII messages

All cases now round-trip cleanly through JSON.stringify/JSON.parse. TypeScript build and Prettier check pass. The 5 pre-existing ESLint errors in src/main.ts (enum shadow, any, English-text rule) are unrelated to this change and present on main as well.

dist/main/index.js rebuilt via npm run package (the action.yml entrypoint points there).