docs: adding algokit template documentation

[negar-abbasi]

No description provided.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
src/algokit
__init__.py	15	7	53%	6–13, 17–24, 32–34
__main__.py	2	2	0%	1–3
src/algokit/cli
completions.py	105	2	98%	80, 95
deploy.py	55	4	93%	34–36, 78
doctor.py	48	3	94%	142–144
generate.py	30	1	97%	49
goal.py	30	1	97%	42
init.py	190	16	92%	264–265, 315, 318–320, 331, 375, 401, 441, 450–452, 455–460, 473
localnet.py	91	3	97%	157, 178–179
src/algokit/core
bootstrap.py	161	24	85%	103–104, 126, 149, 214, 217, 223–237, 246–251
conf.py	54	8	85%	10, 24, 28, 36, 38, 71–73
deploy.py	59	10	83%	60–63, 72–73, 77, 82, 89–91
doctor.py	65	7	89%	67–69, 92–94, 134
log_handlers.py	68	7	90%	50–51, 63, 112–116, 125
proc.py	45	1	98%	98
sandbox.py	150	15	90%	100–107, 118, 226, 242, 257–259, 275
typed_client_generation.py	80	5	94%	55–57, 70, 75
version_prompt.py	73	8	89%	27–28, 40, 59–62, 80, 109
TOTAL	1485	124	92%

Tests	Skipped	Failures	Errors	Time
232	0 💤	0 ❌	0 🔥	17.707s ⏱️

[aorumbayev]

Just final set of comments from my side and we are good to go for this initial version of the tutorial. Unless any further comments from @achidlow or @daniel-makerx

@joe-p feel free to check as well if you have any further suggestions before we merge this. The goal here is to set a starting point for a more detailed doc for template builders (currently we only have a few paragraphs on algokit docs that primarily just forward to beaker repo or copier docs). This doc is set to set more explicit context on templates structure and etc.

[aorumbayev]

Let's add another section called quick start in here before any other sections, because despite overview of the templates itself we still don't directly provide a guide on how exactly to create them for users. So it will serve a quick TL;DR section that users runs over before diving into reading the tutorial because he will need the reference beaker template anyway.

Since we are assuming beaker templates lets do a simple set of numbered items on things that a template builder needs to setup before they read the remaining part of this tutorial.

Something like:

For users who are keen on getting started with creating AlgoKit templates, you can follow these quick steps:

1. Click on `Use this template`->`Create a new repository` on [algokit-beaker-default-template](https://github.com/algorandfoundation/algokit-beaker-default-template) Github page. This will create a new reference repository with clean git history, allowing you to start modifying and transforming the base beaker template into your own custom template. 
2. Modify the cloned template according to your specific needs. You can refer to the remainder of this tutorial for an understanding of expected behaviors from the AlgoKit side, Copier - the templating framework, and key concepts related to the default files you will encounter in the reference template.

@Loedn please note merging this PR assumes we turned the repos to template repos (at least the beaker repository) so this ways folks wouldn't need to Clone-> Clear git history each time but just make a templage repo from base template repo.

[aorumbayev]

@negar-abbasi aside from minor typo comment just one extra ref I think we would want to include is:

On this doc https://github.com/algorandfoundation/algokit-cli/blob/main/docs/features/init.md#community-templates, please modify the:
If you want to create a community template, you can use the [beaker template](https://github.com/algorandfoundation/algokit-beaker-default-template) and [Copier documentation](https://copier.readthedocs.io/en/stable/) as a starting point. to instead point out to this document because that essentially expands a lot on how templates work and how to quick start making your own.

Once addressed I'll approve the changes.

@Loedn so i think devrel is ok with using the templates feature? If yes lmk if you can approve this once template repos have template toggle enabled and we can merge this

[Loedn]

all clear on my end

[aorumbayev]

@Loedn please keep in mind you'd need to turn full stack, react and beaker repos into template repos on github once 1.3.0 release is out