Expand @ocom-verification coverage for Community Management

[nnoce14]

Description
Add comprehensive scenario coverage for the community bounded context. Community updates are already implemented on the ui-community side. All test suites derive step definitions from shared scenarios in verification-shared.

What needs to be implemented

• New or improved shared Gherkin scenarios plus any required supporting step definitions and context extensions.
• Ensure scenarios exercise the domain aggregates, application services, and UI routes effectively.

Scope (specifically scoped shared scenarios)

• Community creation (with validation rules)
• Community updates / editing (name, settings, visibility, description, etc.)
• Permission checks (owner vs member vs staff)

Acceptance Criteria

verification-shared

• Add or significantly improve shared Gherkin scenarios for create, read, and update flows following the project's BDD style.

acceptance-api

• API-specific step definitions covering backend logic, persistence, event publishing, and error handling.

acceptance-ui

• UI-specific steps focused on create and update flows in the ui-community portal, plus any staff portal management views.

e2e-tests

• End-to-end scenarios linking UI actions to API verifications and cross-community assertions.

General

• Some scenarios may already be implemented — review existing ones in verification-shared and adjust/extend them as part of this task as needed so that all necessary scenarios are covered properly going forward.
• Out of scope: Community deletion / archiving (not implemented yet; planned for staff users later).
• Follow existing patterns in verification-shared, reuse contexts/hooks, and maintain compatibility with current mocks and infrastructure.
• Reference recent enhancements in the domain or UI packages.
• Improve overall coverage for community-related code.