feat: transfer ownership of event to another user

[shreyanshdwivedi]

Fixes #3012

Short description of what this resolves:

We are implementing feature to provide ability to a user to delete his/her account. If the user is associated with any event, he/she must be given choice to transfer the events to other organizers associated with the event.

Changes proposed in this pull request:

• Adds a settings option which will have option to transfer ownership of an event to other user
  

Checklist

• I have read the Contribution & Best practices Guide.
• My branch is up-to-date with the Upstream development branch.
• The acceptance, integration, unit tests and linter pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[kushthedude]

@shreyanshdwivedi Just a suggestion , Semantic-UI provides various designing patterns for the UI header and UI Segments and more , See if you can use Red Segments for this section to make it more look-a-like to Github Danger Zone

[shreyanshdwivedi]

@uds5501 @kushthedude I might need some help here. Actually the events-transfer-modal is coming up as plain html rather than being a modal. Can you guys point me what am I missing here?

[kushthedude]

@uds5501 @kushthedude I might need some help here. Actually the events-transfer-modal is coming up as plain html rather than being a modal. Can you guys point me what am I missing here?

@shreyanshdwivedi Incorrect File Name is all the cause buddy 😆

[shreyanshdwivedi]

@kushthedude thanks for pointing out my silly mistake 🤣

[shreyanshdwivedi]

@uds5501 the frontend PR is almost completed now. It only needs the endpoint now. I'm sending the event to be transferred and the email of the new organizer as payload. Please take a look and make the endpoint based on it. And please reference the server PR here

[uds5501]

@shreyanshdwivedi understood, will link the PR over here and carry on the server implementation accordingly

[uds5501]

@shreyanshdwivedi please change the payload to :

        data: {
          attributes: {
            'new-organizer': data.newOrganizerEmail,
            'starts-at'    : event.startsAt,
            'ends-at'      : event.endsAt,
            'timezone'     : event.timezone
          },
          id: event.originalId, 
          type: 'event',
          identifier: event.id
        }

This passes the schema validation checks and I can work on the before_patch hook after this

[shreyanshdwivedi]

@uds5501 I've updated the PR. Also I've changed new-organiser to new-owner. Please update your server implementation accordingly

[mariobehling]

@shreyanshdwivedi Please also update the text about the account deletion:

Your account currently cannot be deleted as active events and/or orders are associated with it. Before you can delete your account you must transfer the ownership of your event(s) to another organizer or cancel your event(s). If you have ticket orders stored in the system, please cancel your orders first too.

[shreyanshdwivedi]

@uds5501 @CosmicCoder96 This PR is completed now. I've implemented a role-invite for transferring event and opened a server PR for handling role invite for owner role - fossasia/open-event-server#6048
These both PRs can be merged only after owner is added as a role on server via this PR - fossasia/open-event-server#6042

[shreyanshdwivedi]

@CosmicCoder96 I've made the required change. Please review

[shreyanshdwivedi]

@CosmicCoder96 updated the async-await logic. Please review

[shreyanshdwivedi]

@CosmicCoder96 @niranjan94 please review

[shreyanshdwivedi]

@niranjan94 I've made the changes. Please review

[shreyanshdwivedi]

@niranjan94 added eventName to computed properties. Please check

[niranjan94]

@shreyanshdwivedi this PR contains DO-NOT-MERGE label. Is the label still valid ?

[shreyanshdwivedi]

Let's not merge it for now. It depends on PR fossasia/open-event-server#6042
Please review it too @CosmicCoder96 @niranjan94
It is a big change so needs a thorough check