[Templating] Expose warnings/errors to callers

[anna-dingler]

Related Issue

Fixes #7433

Description

TLDR

Warnings need to be exposed to the caller instead of logged in the console.

Proposed Solution

C#
Add optional out parameters to the AdaptiveCardTemplate.Expand methods that's an array of warning strings

JS
Add an overload for the Template.expand method that takes an out parameter that's an array of warning strings (or alternatively, maybe an optional out parameter?)

In this PR

I added an optional parameter for an array of warning/error strings to the expand method of the JS library.

For the .NET library, I added an out parameter for the warning/error string array to the Expand methods. I also added an additional wrapper methods, that call the updated Expand methods to ensure this isn't a breaking change.

Sample Card

These cards should produce warning strings if the proper expand method is called.

Test 1 - Not an Expression

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "size": "Medium",
            "weight": "Bolder",
            "text": "${title}",
            "$when": "NotAnExpression"
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.5"
}

Test 2 - Invalid Expression No Data

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "size": "Medium",
            "weight": "Bolder",
            "text": "${title}",
            "$when": "${InvalidExpression}"
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.5"
}

Test 3 - Invalid Expression with Data

Card

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "size": "Medium",
            "weight": "Bolder",
            "text": "${title}",
            "$when": "${InvalidExpression}"
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.5"
}

Data

{
   "test": "dummyData"
}

How Verified

Verified with the unit tests added with this PR.

Microsoft Reviewers: Open in CodeFlow

[ghost]

Hi @anna-dingler. Thanks for helping make the AdaptiveCards JS renderer + tooling better. As additional verification, once the JS build succeeds, please go to the test site to test out your website/designer changes.

[jwoo-msft]

we have a lot of Expand methods, can you somehow consolidate it. at minimum, can you make sure the primary Expand method is at the prominent place, so devs would know which one is the primary one without much of a search?
and if you could, it would be nice if we can reduce the number ArrayList instantiation. So if we are going to change log data structure, we could do it at one place.

[anna-dingler]

we have a lot of Expand methods, can you somehow consolidate it. at minimum, can you make sure the primary Expand method is at the prominent place, so devs would know which one is the primary one without much of a search? and if you could, it would be nice if we can reduce the number ArrayList instantiation. So if we are going to change log data structure, we could do it at one place.

I grouped the wrapper methods together and left additional comments to the Expand methods to make it clearer. I also used _ to indicate a discarded out parameter to cut down on ArrayList instantiation.

Should I be committing the autogenerated .md files fot the .NET library?