Plots2: Add an indicator for red colored banned users and a hover over the username to check for spammers quickly

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

The problem

When you go to page:

http://localhost:3000/likes

You see something like this:

Here, The recent likes are listed with banned users depicted in red colour and black otherwise. There should be an indicator as to what red indicates. Secondly, a hover for admin and moderators is required over the username so that they can read peoples' bio quickly to check if they're spammers.

Solution

The changes are required to be made in the following template:

https://github.com/publiclab/plots2/blob/master/app/views/like/index.html.erb

Add the indicator for red coloured banned user in <p> tags below the heading Recent Likes in this template something like this:

<p>Username in red indicates <b><i>banned user</i></b>.</p><br>

Secondly, a hover over the username for moderators and admin only could be implemented by adding an if else condition to check for admin and moderators like this:
````ruby
<% if current_user && (current_user.role == "admin" || current_user.role == "moderator") %>

<%= like.user.name %>

<% else %>

<%= like.user.name %>

<% end %>
````
replacing this line of code https://github.com/publiclab/plots2/blob/3955e17ad30eda37854d97d7813a862060d2bbfd/app/views/like/index.html.erb#L16

Steps to Fix

• [ ] claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] set up a repository locally following the README instructions, and make sure that all tests pass
• [ ] try to fix the issue following the steps above, but even before you're done, you can:
• [ ] commit your changes and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
• [ ] alert someone via the developers list (see below) to have your pull request merged. This may take a few extra steps depending on when you do it, but we'll help you out!

Please email the developers list (see https://publiclab.org/wiki/developers) or go to the chatroom if you have questions, and take a look at our first-timers landing page for more information!