Add /disablecommunity and /enablecommunity commands for superadmins

[mostronatorcoder]

Add two new superadmin-only commands to control whether a community is active or not:

• /disablecommunity
• /enablecommunity

Implementation requirements:

• Add a new field to the community.ts model: enabled: boolean.
• When enabled is true, the community behaves normally.
• When enabled is false, the community must remain in the database but be completely inaccessible to:
• regular users
• community admins
• orders and any related flows

In practice, a disabled community should behave as if it does not exist from the user's perspective.

The /enablecommunity command should allow a superadmin to restore a previously disabled community, making it fully usable again.

[grunch]

This issue doesn't say what close the community means. Does it mean deleting it or adding a new field to disable it?

I think we should change "close" to "disable" so we can deactivate and reactivate it if needed, and keep the data in the database in case we need to do an audit.

[ToRyVand]

Hi @grunch, can I take this issue?

[Luquitasjeffrey]

Closed on #817