docs: deprecate create-eth extensions

[rin-st]

What

Mark create-eth extensions as deprecated across the docs. No code changes — extensions still ship and work for now; this is docs-only, with removal to follow in a later phase.

Changes

• CONTRIBUTING.md — drop the "create a PR to the example extension branch" contributor guideline.
• contributors/THIRD-PARTY-EXTENSION.md — add a deprecation banner ([!WARNING]); guide kept for existing extension authors.
• contributors/TEMPLATING.md / TEMPLATE-FILES.md — add deprecation note ([!NOTE]); templating mechanics kept, since create-eth still uses the template/args system internally to assemble instances.
• contributors/DEVELOPER-GUIDE.md — reframe the templating intro away from extension-authoring; mark the args-sync checklist item (optional, deprecated).

All deprecation notes point users to skills as the replacement: https://docs.scaffoldeth.io/build-with-ai

Removed extensions from .github/workflows/lint-instances.yml:

• Matrix reduced from 6 → 3 configs: [hardhat, foundry, no_solidity_framework] (dropped the three _with_extension variants).
• Removed the 3 "Install application … with extension" steps.
• Simplified the 6 if: conditionals that referenced _with_extension.

Notes

• The user-facing README note (skills instead of extensions) is not in this PR — it'll land in scaffold-eth-2 and reach create-eth via backmerge.

🤖 Generated with Claude Code

[technophile-04]

I was wondering maybe it's good idea to keep some of it? This would be helpful for the challenges? Since we are still using the extension?

[rin-st]

I wrote about it here scaffold-eth/create-eth-extensions#124 (comment), this part

The only extension we use from this repo is example extension, which is used in gh actions of create-eth to test if new create-eth version works fine with extensions at all. Since currently we just need to know if create-eth works fine with SRE extensions, it would be good to switch create-eth gh actions to be tested with sre tokenization-challenge extension. But, sre extensions always bound to some create-eth version. And if some create-eth change will break compatibility with sre extension it's not so obvious which steps to do and in which order to update both create-eth, sre-challenge and keep gh action green. So I think we just need to remove from gh actions extensions part.