Meatball menu for converstaion view controls

[nichgalzin]

Expected Behavior

Controls for conversations, including deleting conversations, showing messaging rule and blocking users are contained in a meatball menu.

In mobile view it lives in the mobile header:

In desktop it lives in the reservation card:

Scope:

• The scope of this issue can ignore the functionality and styling of parent containers (i.e. header or reservation card) and should focus just on the menu and functionality of its options.
• Blocking users is not currently implemented and can be excluded (see issue Blocking other users #99)
  This issue relies on Message specific header for mobile view #430

Acceptance Criteria

• The meatball menu menu should be self contained and able to be insert into the relevant components (see above).
• The existing feature that have logic (i.e. deleting conversations and showing the rules should be function and use the existing state and utils/models that handle this functionality).
  - Where possible existing components should be used / or refactored.
  - Components should be self contained and have a corresponding storybook file. Story book files should be updated where required.
  - Styling should match the designs in Figma and use the matching colour variables outline in the tailwind config file.
  - Component should be responsive and should match layout designs for mobile and desktop (see Figma file)
  all messaging functionality and validation should continue to work
  - Any e2e test that already exist should pass and new one should be added as necessary

Assignment

This issue is free for anyone to take