Remove archived samples from CI build matrix and added TeamsSDK sample builds

[Harikrishnan-MSFT]

PR Description:

Summary
This PR performs two sets of changes:

1. Archived sample removal from CI — Removes individual GitHub Actions workflow files and build matrix entries in build-complete-samples.yml for samples planned for archival, across all applicable language targets (C#, Node.js).

2. TeamsSDK sample build fixes — Fixes CI buildability for TeamsSDK Node.js and Python samples by adding missing tsconfig.json, build scripts, TypeScript devDependency, correcting python-dotenv version specifiers, and applying an optional chaining fix in bot-task-modules.

Changes

Archived samples removed from CI (~85 workflow files deleted):

• Deleted individual .github/workflows/*.yml files for all archived samples (app-, bot-, graph-, meeting, msgext-, tab-, typeahead-*, etc.)
• Removed corresponding entries from .github/workflows/build-complete-samples.yml

TeamsSDK sample fixes:

• Added tsconfig.json (ES2022/Node16 config) to: bot-ai-messages, bot-attachments, bot-cards, bot-meetings, bot-message-extensions, bot-quickstart, bot-task-modules (Node.js)
• Added "build": "tsc --build" script and typescript ~5.8.3 devDependency to the above package.json files
• Fixed python-dotenv version specifier: >=1.0.* → >=1.0 in Python pyproject.toml files
• Added [tool.setuptools.packages.find] to bot-auth-quickstart and bot-task-modules Python projects
• Fixed optional chaining: app.http.use(...) → app.http?.use(...) in bot-task-modules/index.ts

No functional code changes to sample logic.

[lilyydu]

May have missed this but are we going to be adding new workflows for the new samples? And do we need to fix any configs for the C# samples (noticed these new changes only capture TS/PY)

[Harikrishnan-MSFT]

May have missed this but are we going to be adding new workflows for the new samples? And do we need to fix any configs for the C# samples (noticed these new changes only capture TS/PY)

The existing workflow has been updated to include Teams SDK samples for all three languages.
Filename: build-complete-samples.yml

`
csharp -

NodeJS -

Python -

[lilyydu]

does this just ensure that the samples build correctly? wondering if we can incorporate dependabot to check for package versioning and perform the necessary updates also

[Harikrishnan-MSFT]

does this just ensure that the samples build correctly? wondering if we can incorporate dependabot to check for package versioning and perform the necessary updates also

Yes @lilyydu, We plan to implement this concept in the next PR. We can merge this PR and open a new one for those changes.

[Harikrishnan-MSFT]

https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/25102196709