docs: move docs for telescope repo from docs repo into the telescope

[Anmol1696]

• add gh-action to sync docs back

[Copilot]

Pull Request Overview

This PR moves Telescope’s documentation from a separate docs repository into the Telescope repo and adds a GitHub Action to sync the docs back. Key changes include new and updated MDX documentation files for various sections and the addition of a workflow file in .github/workflows/docs.yaml.

Reviewed Changes

Copilot reviewed 26 out of 26 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
docs/index.mdx	New main documentation file for Telescope.
docs/get-started.mdx	Adds getting started instructions with code generation, installation, and build tips.
docs/developing/working-with-asts.mdx	Minor typo fix in the description regarding the npm module usage.
docs/developing/tree-shakable-hooks.mdx	Updates example code to use the new createGetBalance function; includes minor text changes.
docs/developing/tests.mdx	Fixes a typo in the test instructions.
docs/developing/migration.mdx	Fixes spelling mistakes in configuration option descriptions.
docs/developing/helpers.mdx	Updates documentation text for clarity in describing the addUtil usage.
docs/developing/creating-new-generators.mdx	Simplifies the generators documentation.
docs/_meta.json	Adds metadata for the docs structure.
docs/README.md	Removes the old README as the docs are migrated.
.github/workflows/docs.yaml	Introduces a new GH Action workflow to sync and deploy the docs.

[Copilot]

[nitpick] Consider improving phrasing: change 'is recommend' to 'is recommended' and 'without worrying repetitive import' to 'without worrying about repetitive imports'.

Suggested change

	when generating code, sometimes we need to import helpers, utils or packages. In that case, using addUtil method in context when building ast is recommend, since we only add utils as needed without worrying repetitive import:
	when generating code, sometimes we need to import helpers, utils, or packages. In that case, using the addUtil method in context when building the AST is recommended, since we only add utils as needed without worrying about repetitive imports: