Design for `Report`s and `Pending Suggestion`s for a Resource

[marcbachan]

Description

Per discussion with @lxh5395 , we should communicate some qualitative information from the crowdsourced suggestions, namely:

• whether the information has been reported (i.e., as erroneous or outdated)
• whether there are pending edits, and some indication of how many (i.e., "there are a few suggested edits", "there are a number of suggested edits" for a resource)
• to avoid overwhelming the user, these will be in a collapsed view by default, opened voluntarily

For a visual example for what this could look like, see slide 4 here: https://docs.google.com/presentation/d/1qrvpBtS5niJ1EFnjK7bfAuH2-XwZJKfSfF4gydZ-ovg/edit?usp=sharing

Complexity

@lxh5395 please advise on effort for wireframes. @vontell There are implications here for feasibility on the data side.

[lxh5395]

Including some screen shots to better explain how to display the warnings for pending items @RRodriguez26

[RRodriguez26]

Desktop Design can be found here, inside of Raf's Space https://www.figma.com/design/VGGqwl3Eq3GQIAO9I6LoNW/PHLASK?node-id=4510-29556

[gcardonag]

@RRodriguez26 , I caught up with @lxh5395 last week to walk them through the design in your space. I think the only feedback pending was to look into aligning the designs to the spacing that they had shared and some of the colors didn't quite line up with our PHLASK-specific palette. If you'd like to go into it in some more detail, I would recommend reaching out to Logan to do a 1-on-1 design review session