[Contribution initiative] Add tutorial content type

[leemthompo]

Closes https://github.com/elastic/docs-team/issues/114

DONE:

• Drafted main guide page
• Disambiguation snippet included in both how-tos.md and tutorials.md
• Two example tutorials linked (provisionally ES|QL threat hunting and ES|QL search, will hive mind for alternative examples 😀)

TODO:

• Template

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

2.Tool(s) and model(s) used:

Claude Code, Opus 4.1 for autocomplete on steroids and grunt work automation

[github-actions]

Vale Linting Results

Summary: 1 warning, 13 suggestions found

⚠️ Warnings (1)

File	Line	Rule	Message
contribute-docs/content-types/tutorials.md	85	Elastic.DontUse	Don't use 'just'.

💡 Suggestions (13)

File	Line	Rule	Message
contribute-docs/content-types/_snippets/templates/tutorial-template.md	2	Elastic.FutureTense	'will learn' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/_snippets/templates/tutorial-template.md	16	Elastic.FutureTense	'will learn' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/_snippets/templates/tutorial-template.md	37	Elastic.FutureTense	'you'll learn' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/_snippets/templates/tutorial-template.md	42	Elastic.FutureTense	'you'll be' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/_snippets/templates/tutorial-template.md	44	Elastic.EmDashes	Don't put a space before or after a dash.
contribute-docs/content-types/_snippets/templates/tutorial-template.md	58	Elastic.FutureTense	'You'll need' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/tutorials.md	39	Elastic.FutureTense	'They'll find' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/tutorials.md	39	Elastic.Exclamation	Use exclamation points sparingly. Consider removing the exclamation point.
contribute-docs/content-types/tutorials.md	44	Elastic.Wordiness	Consider using 'complete' instead of 'successfully complete'.
contribute-docs/content-types/tutorials.md	44	Elastic.FutureTense	'they'll learn' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/tutorials.md	44	Elastic.FutureTense	'they'll achieve' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/tutorials.md	54	Elastic.FutureTense	'will learn' might be in future tense. Write in the present tense to describe the state of the product as it is now.
contribute-docs/content-types/tutorials.md	60	Elastic.FutureTense	'will learn' might be in future tense. Write in the present tense to describe the state of the product as it is now.

[github-actions]

🔍 Preview links for changed docs

• contribute-docs/content-types/tutorials.md
• contribute-docs/content-types/how-tos.md

[leemthompo]

Reviewer: I've nested admonitions: love it or hate it?

[leemthompo]

Use exclamation points sparingly.

One exclamation point is as sparing as one can be 😄

[leemthompo]

Zero attachments to these specifically, and we wouldn't want two ESQL examples here, but they illustrate the two different flavors I've tried to tease out here (feature-focused versus scenario-driven tutorials) and they hew pretty close to the best practices.