feat(ocm): implement WAYF page and enhance invitation workflow

[MahdiBaghbani]

This PR is a part of cs3org/OCM-STA#1

This PR depends on this PR cs3org/reva#5385 to be merged in Reva.

Description

This PR implements the frontend components for WAYF (Where Are You From) functionality in the OCM web application, enabling users to discover and select their cloud provider when accepting federated invitations. The implementation provides a user friendly interface for OCM provider selection and complements the backend WAYF discovery endpoints.

Technical

Things I've added to the web application:

• WAYF Page: Provider selection interface with federation browsing and manual provider entry
• WAYF is public page: Public access to WAYF page without authentication requirement
• Invitation Acceptance Modal: Component for invitation acceptance workflow from other EFSS WAYF Pages
• Token Management: Multiple copy formats (plain, base64, WAYF link) for outgoing invitations
• Self-Domain Prevention: Prevent users from selecting their own instance
• Shared Composables: Reusable logic for invitation acceptance and WAYF functionality
• Federation list display with automatic grouping
• Manual provider domain entry with OCM discovery

Code Changes

• New Components:

  • src/views/Wayf.vue: Main WAYF page with provider selection UI, search functionality, and federation display
  • src/views/InvitationAcceptanceModal.vue: Modal component for accepting invitations with provider validation

• New Composables:

  • src/composables/useWayf.ts: Core WAYF logic including federation loading, provider discovery, and self-domain validation
  • src/composables/useInvitationAcceptance.ts: Shared invitation acceptance logic with self-generated token detection

• New Types:

  • src/types/wayf.ts: TypeScript interfaces for federation and provider data structures

• Updated Routing (src/index.ts):

  • Added /wayf route with authContext: 'anonymous' for public access
  • Added /accept-invite route for invitation acceptance workflow
  • Included authentication context documentation

• Modified Views:

  • src/views/OutgoingInvitations.vue: Added three token copy options (plain, base64, WAYF link) with visual improvements
  • src/views/IncomingInvitations.vue: Refactored to use shared useInvitationAcceptance composable
  • src/views/ConnectionsPanel.vue: Minor UI adjustments
  • src/views/App.vue: Updated to support new routes

• Documentation:

  • docs/Where Are You From page.md: WAYF usage guide, API endpoints, and testing scenarios

Videos of the changes and general flow of the OCM app

From CERNBox to OpenCloud

From CERNBox to OpenCloud

[glpatcern]

Hi Mahdi, how different is this PR from the one you submitted to ownCloud? Ideally they should be the same, and in this case as we adopt the upstream web extensions we would not need this one!

[MahdiBaghbani]

I think that CERNBox is a major version behind and there are different setup behavior in the vue.js files across both apps, see:
https://github.com/MahdiBaghbani/web/blob/521e80b0ae7732c3da12bd9bae43496d2b981459/packages/web-app-ocm/src/views/Wayf.vue#L159

versus:
https://github.com/MahdiBaghbani/web/blob/5b311de6d4624112a7cf3ca277de94a95f500c5a/packages/web-app-ocm/src/views/Wayf.vue#L154
https://github.com/MahdiBaghbani/web/blob/5b311de6d4624112a7cf3ca277de94a95f500c5a/packages/web-app-ocm/src/views/Wayf.vue#L168-L181

also they use global store to cache the generated tokens as well via piniaStore, see: https://github.com/MahdiBaghbani/web/blob/521e80b0ae7732c3da12bd9bae43496d2b981459/packages/web-pkg/src/composables/piniaStores/inviteTokensList.ts#L1-L45

If this can be waited and you will migrate to the upstream, then yes this can be done via the ownCloud