New Repo: `educational-game`

Use this issue type to request a new repo in `knative-extensions` (or
`knative`, which may require additional discussion).

## Repo information

Org: `knative-extensions`

Repo: `educational-game`

Go module (Optional): N/A, this will be a [godot](https://godotengine.org/) project

Purpose (Description): An educational game to teach Knative concepts, primarily focused around Event Driven Architectures

Sponsoring WG: UX

## Actions to fulfill

This area is used to track the [repo creation process](https://github.com/knative/community/blob/main/mechanics/CREATING-AN-EXTENSIONS-REPO.md).
The _requestor_ and _sponsoring WG lead_ should perform the steps listed below and cross out the checkmarks when done.
The TOC is involved only in the **TOC Gate** steps.

- [x] Add this issue to the [TOC project board](https://github.com/orgs/knative/projects/43) for review. You are responsible for moving your entry on the board to "Needs Discussion" or "In Progress" as you move forward in this checklist.

_You may not be able to use the Projects quick menu on this page. In that case, go to the project board and use the **Add cards** interface._

- [x] Send a PR adding entries for this repo in [`/peribolos/knative-extensions.yaml`](https://github.com/knative/community/blob/main/peribolos/knative-extensions.yaml). Please mind the alphabetical order when adding to a list.
- [x] Add the repository and a description.
- [x] Grant `Knative Admin` the `admin` privilege.
- [x] Grant the sponsoring WG the `write` privilege.

**TOC Gate**: _Once the TOC has approved the above, it will merge and Peribolos will create an empty repository._

- [ ] (golang) Send a PR to add aliases for `knative.dev/$REPONAME` import paths ([sample](https://github.com/knative/docs/pull/4160)).

- [ ] Have a lead from the sponsoring WG bootstrap the Git repository by using an
appropriate "template" repository ([basic](https://github.com/knative-extensions/wg-repository),
[sample-controller](https://github.com/knative-extensions/sample-controller),
[sample-source](https://github.com/knative-extensions/sample-source)).

Follow the instructions from [Creating a repository from a template](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)

- [ ] Send a PR adding the repo to [knobots](https://github.com/knative-extensions/knobots). Then run the community files update action to propagate new OWNER_ALIASES.

- [ ] Add your GitHub Team to the `OWNERS` file for your repo.

- [ ] [Set up](https://github.com/knative/test-infra/blob/main/guides/prow_knative_setup.md#setting-up-prow-for-a-new-repo-reviewers-assignment-and-auto-merge) prow for a new repo

- [ ] Bootstrap your CI jobs using [hack](https://github.com/knative/hack) project (look at other extensions repos for reference)

- [ ] Create a sample PR to verify Prow (e.g., edit the boilerplate README)

- [ ] Verify that within 24 hours the appropriate branch protections have been applied
requiring `tide` to pass before PRs are merged.

- [ ] (optional) Send a PR adding the repo to [CLOMonitor](https://clomonitor.io/projects/cncf/knative) ([more information](/REPOSITORY-GUIDELINES.md#clomonitor-and-clotributor)).

Start with the repo-creation checklist in this issue and the linked mechanics/CREATING-AN-EXTENSIONS-REPO.md guidance. Review the completed peribolos/knative-extensions.yaml step, then follow the remaining bootstrap, knobots, OWNERS, Prow, and CI actions. Done means the repository is created and its listed governance, automation, protection, and verification steps are complete.

Written by the indexing model from the issue text.