Refactor command "context" system & Support User Apps

[ghostdevv]

• Move the context settings into a nested object
• breaking: Make global the default

[ghostdevv]

Ideas for the nested object setting

context?: {
	/** @default true */
	global?: boolean;
	
	/** @default false */
	dm?: boolean;

	/** @default false */
	user?: boolean;

	/** @default [] */
	guilds?: string[] // todo should this be able to accept an async function? if so when should that run
}

Another idea from old issue:

environments: ['global', 'dm', 'user']

[ghostdevv]

worth considering the learning curve each approach adds

[ghostdevv]

To move forward I need to consider:

• What contexts Discord "defaults" to?
• Whether requiring you to be explicit is ideal (to reduce potential confusion)?
• Are any contexts mutually exclusive?
• Should we allow overwriting the defaults on a global level? (maybe should require users do with a transform plugin, if those are re-added)