Description
The Wikidata team would like EntitySchemas (EnSc) to be returned as a wikibase entity as part of the larger goal of allowing statements linking to EntitySchemas in Items.

With this, Wikidata hopes to have more consistent data modelling, a uniform user experience and for the community members to have an easier time working with EntitySchemas in their day-to-day work. With the latter, i.e., allowing current tools to not break, being of the highest priority.

Acceptance criteria:

1. Create an approach that allows the WD team to return EnSc as a wikibase-entity without creating more dependencies or too many hacky short-term solutions in the codebase.
2. Approach in 1. is built keeping in mind the other requirements that go into the original goal of WD listed above. A list of these can be found in the WD epic ticket linked below or in the document here
3. This is ideally built in a way that then allows the following things to be developed as a next step (in the short-term future) without having to redo the approach in 1. :
   1. Ability to have statements on EntitySchemas
   2. Ability to create new UX / UI patterns
   3. Expanding the functionality of EntitySchemas to create or edit existing Items
   4. Merging duplicate EntitySchemas
   5. Lua access

1. Approach allows for the implementation to be done by WD before June 2024.

Summary of relevant documents to the topic

1. EntitySchema PRD from WD
2. Leszek's list of what is involved in linking an EntitySchema to an item with a statement
3. WPP Pre-morten document
4. EntitySchema list of use cases