Feature/add rich text reaction model

[wwrk22]

What's the change?

Added a model that stores emojis for reacting to standup meeting updates. The backend implementation was done on this branch.

What key workflows are impacted?

Users can create RichTextReaction records via the console to emulate reacting to standup meeting updates.

Highlights / Surprises / Risks / Cleanup

The frontend implementation that includes the UI to allow users to react is still required.

Demo / Screenshots

Create reactons via the Rails console.

# Assume current_user is the signed-in User, and rich_text_id is the id of an ActionText::RichText record.
rich_text_id = StandupMeeting.where(user: current_user).yesterday_work_description.id

# Refer to RichTextReaction.emojis for emojis that can be used in creating reactions.
current_user.rich_text_reactions.create(rich_text_id:, emoji_caption: ‘thumbs_up')

Issue ticket number and link

#212
This PR does not completely resolve the issue.

Checklist before requesting a review

Please delete items that are not relevant.

• Did you add appropriate automated tests?
• Did you consider risks around security, performance, etc.?
• Have you thought of misfiring code? e.g. too many loops, n+1, or how to handle nils?
• Any validations to data needed?
• Related to readability and consistency: Did you add comments and/or documentation? (README, Notion, etc.)
• Is everything elevated to the highest level? (e.g., can logic be moved out of view into controllers, or out of controllers into models?)
• Can (and should) any models be extracted?
• Is there any linting that needs to be executed?
• Did you leave helpful inline PR comments for the reviewer(s)?
• Did you include instructions for how to test in the ticket?
• Did you add any relevant tags and decide if this PR is a Draft vs. Ready for Review?
• Do you have a plan for how this change should be rolled back? (e.g., how do you deal with a migration rollback? Is your feature released behind a feature flag?)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2fc41b0) 98.94% compared to head (008127f) 98.97%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #451      +/-   ##
==========================================
+ Coverage   98.94%   98.97%   +0.02%     
==========================================
  Files         209      216       +7     
  Lines        3231     3321      +90     
==========================================
+ Hits         3197     3287      +90     
  Misses         34       34              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jp524]

In the Demo / Screenshots section of the PR, last line should read current_user.rich_text_reactions.create(rich_text_id:, emoji_caption: :thumbs_up) since emoji was changed to emoji_caption in the schema.

[wwrk22]

In the Demo / Screenshots section of the PR, last line should read current_user.rich_text_reactions.create(rich_text_id:, emoji_caption: :thumbs_up) since emoji was changed to emoji_caption in the schema.

Fixed

[JoshDevHub]

Just one reminder of something to fix in here. The other stuff looks really good though.

[wwrk22]

@JoshDevHub
Some ActiveRecord model object has to be given for creating ActionText::RichText.
I decided the User model is probably the safest to use since it most likely won’t be going away or changed to a different name.

[wwrk22]

@JoshDevHub
I think unless we can somehow have a fake ActiveRecord model with a fake database table, it’s best to skip linting the ActionText::RichText factory.

[JoshDevHub]

Alright cool. Looks like you have to fix some merge conflicts and it'll be good to go

[wwrk22]

@JoshDevHub
Per the comment above:
Merge conflict has been resolved.