[Discussion] Tooling for generating samples, tests, and other assets for client emitters

[xirzec]

Creating this issue as a place to discuss tooling for generating samples, tests, and other assets as part of SDK client generation.

We have been exploring this space for Azure SDKs, but would like to get feedback from others using TypeSpec to know if there is a general need/desire for similar tooling.

Some starter questions:

1. Is it better to hand-author samples/tests/etc in one language and then translate to others or to use natural language to describe the scenarios when authoring the spec?
2. What kinds of tests would be most useful (e.g. functional validation of the model shape/payload or end-to-end scenarios of ensuring basic functionality works as expected.)
3. How frequent/expensive is this task? For example, Azure has many (100+) resource management SDKs to support across 5+ languages, but perhaps this is a specific challenge of Azure.

[markcowl]

@markcowl link to Azure-specific issue and use this to represent the core parts required for support, and the parts that are of general use to all APIs