Feat/add app metadata controller

[frankvonhoven]

Explanation

Porting over the AppMetadataController from Extension

References

Changelog

@metamask/package-a

• : Your change here
• : Your change here

@metamask/package-b

• : Your change here
• : Your change here

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[mikesposito]

I see that this controller has no public method, how do we intend the client to interact with this package?
I just realized that the extension is already using the package via the constructor alone, which I feel is a little weird, but I guess goes beyond the scope of this PR

[mikesposito]

Can we set the version to 0.0.0 until the first release?

Suggested change

	"version": "1.0.0",
	"version": "0.0.0",

[mikesposito]

Are these dependencies used?

Suggested change

	"@metamask/base-controller": "^8.0.0",
	"@metamask/rpc-errors": "^7.0.2",
	"@metamask/utils": "^11.1.0",
	"nanoid": "^3.3.8"
	"@metamask/base-controller": "^8.0.0"

[mikesposito]

nit: Perhaps we can specify what maybe means in the jsdoc:

Suggested change

	/**
	* Updates the currentAppVersion in state, and sets the previousAppVersion to the old currentAppVersion.
	*
	* @param maybeNewAppVersion
	*/
	/**
	* Update `currentAppVersion` in the controller state if the provided value
	* is different from the current one. When the value is updated, the previous
	* value is stored in `previousAppVersion`.
	*
	* @param maybeNewAppVersion - The new app version to set.
	*/

[mikesposito]

I see that these were simply moved from the extension, but this suggestion will fix the failing CI (or at least part of it)

[mikesposito]

nit: similarly to the other function:

Suggested change

	/**
	* Updates the migrationVersion in state.
	*
	* @param maybeNewMigrationVersion
	*/
	/**
	* Update `currentMigrationVersion` in the controller state if the provided value
	* is different from the current one. When the value is updated, the previous
	* value is stored in `previousMigrationVersion`.
	*
	* @param maybeNewMigrationVersion - The new migration version to set.
	*/

[mikesposito]

Could we add a root src/index.ts that exports the relevant objects?
i.e.

// src/index.ts
export * from './AppMetadataController`

[mikesposito]

We should also add these changes to configuration files:

• .github/CODEOWNERS for assigning the relevant owners to this package
• tsconfig.json and tsconfig.build.json for adding the package to the workspace

Also, README should also be updated by running yarn update-readme-content