feat: add tags to events

[Dun-sin]

Fixes Issue

Closes #5832

Changes proposed

• add tags to events

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• All new and existing tests passed.
• This PR does not contain plagiarized content.
• The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

[amandamartin-dev]

Hey dunsin! Looking good so far. I have a few notes and one oddity that may be due to my environment but will require another maintainer to test.

1. In adding the tags, the UI form for adding an event has been altered. Please maintain the 1-column layout for now as no design changes should be part of this issue. If you would like to propose design changes here, we can handle that separately.
2. The labels for are missing in the add event form
3. When I was testing, although I can add an event and see the tags in the preview, on save I cannot see them live. This may be my environment as I had issues on another PR related to events seeing the updates (testing in gitpod) - needs confirmation from another maintainer
4. attempted testing to see what happens when duplicate URL events with different tags are merged - unsuccessful due to the issue above.

Images for clarity - please let me know if you need any more detail. Thank you for working on this.

[Dun-sin]

Hey dunsin! Looking good so far. I have a few notes and one oddity that may be due to my environment but will require another maintainer to test.

1. In adding the tags, the UI form for adding an event has been altered. Please maintain the 1-column layout for now as no design changes should be part of this issue. If you would like to propose design changes here, we can handle that separately.
2. The labels for are missing in the add event form
3. When I was testing, although I can add an event and see the tags in the preview, on save I cannot see them live. This may be my environment as I had issues on another PR related to events seeing the updates (testing in gitpod) - needs confirmation from another maintainer
4. attempted testing to see what happens when duplicate URL events with different tags are merged - unsuccessful due to the issue above.

Images for clarity - please let me know if you need any more detail. Thank you for working on this.

@amandamartin-dev for the review:

1. I didn't change anything UI based in adding an event, except where to add the tags and I followed the instruction on where to put it from the issue itself, I'm kind of unclear as to where this UI change is really coming from, please clarify
2. It's unclear what you mean you would have to clarify too.

[amandamartin-dev]

1. I didn't change anything UI based in adding an event, except where to add the tags and I followed the instruction on where to put it from the issue itself, I'm kind of unclear as to where this UI change is really coming from, please clarify

For point 1 - you have added a new div but if you take a look at the structure of the form, the CSS on the new div is different - this is likely the culprit. Take a look and see what you find and if you are stuck, I can help a little later.

2. It's unclear what you mean you would have to clarify too.
   For this one, take a look at production and compare with your local version. You will notice that each form field has a label that is visible in production. This should be maintained in the update.

Production:

PR version:

[Dun-sin]

1. I didn't change anything UI based in adding an event, except where to add the tags and I followed the instruction on where to put it from the issue itself, I'm kind of unclear as to where this UI change is really coming from, please clarify

For point 1 - you have added a new div but if you take a look at the structure of the form, the CSS on the new div is different - this is likely the culprit. Take a look and see what you find and if you are stuck, I can help a little later.

2. It's unclear what you mean you would have to clarify too.
   For this one, take a look at production and compare with your local version. You will notice that each form field has a label that is visible in production. This should be maintained in the update.

Production:

PR version:

Interesting because that's how it looked like when I did run it the first time without adding anything🤔 but it could also be from me I'm going to do two things: check the PR code for anything that I know for a fact I didn't add, the second thing would be to go to the code and uncomment the JSX change I did, if it makes a difference or it doesn't I will let you know.

[Dun-sin]

I'm off the coding grid atm so couldn't do anything, thanks for the help @eddiejaoude

[eddiejaoude]

No worries @Dun-sin

[eddiejaoude]

The tag component is expecting an onClick event, so has a hover state

Using the tag simple component I think would be better here, later if we add an on click event we can change it back

[eddiejaoude]

Thank you 👍

I will address the remaining comments via a temporary branch

I will address via temporary branch