MM-40214: Add App Bar icon

[agarciamontoro]

Summary

This PR adds a new icon explicitly for the App Bar, so that when it is enabled, the proper icon is shown. The logic for rendering the channel header icon or the App Bar one is in the webapp, not here.

I needed to do a couple of things to build this locally:

• Use node 14.
• Run go get -u golang.org/x/sys, which is added in the first commit.
• Use the fix from this open PR. I have not added that as a commit here to avoid conflicts in that other PR, but if you're building locally, note that you may need it.

I also added a commit to fix CI, adding the --verbose solution we've used in other plugins to avoid CI from timing out.

Demo

jitsi.mp4

Ticket Link

https://mattermost.atlassian.net/browse/MM-40214

[agarciamontoro]

Note that we're aiming to release a new version of the plugin with this PR before the release of v7.0 on June 15 (Wednesday next week).

[agarciamontoro]

Swapping Daniel with Lev because Daniel's out today and tomorrow.

[mickmister]

Thanks Alejandro!

[agarciamontoro]

@mickmister, I pushed a change to the estlint rules just 30 seconds after you reviewed 😂 I think it's sensible, since otherwise the following block returns an error:

const action = (channel: Channel) => {
    store.dispatch(startMeeting(channel.id));
};

But I wanted you to take a look. That's why I'm asking for a re-review :)

[agarciamontoro]

Heh, CI is failing because of the error solved in #211. @DHaussermann, if you can take a look at that PR before this one so I can merge that fix in my branch, that'd be awesome. Let me know if you need anything from me, please!

[larkox]

go mod tidy does not get rid of this?

[agarciamontoro]

Nope, I just tried.

[DHaussermann]

Tested and passed

• Icon is registered on the App Bar
• Icon will fail-over to channel header when the App Bar is disabled
• Icon is functional
• Icon tooltip is correct
• Icon has good contrast in all themes
  LGTM!

Sorry for the delay on this @agarciamontoro

[DHaussermann]

@agarciamontoro this is good to merge but depending on when a release with this is needed, we may need to package a separate release with this change.

[agarciamontoro]

@DHaussermann, thank you very much!

this is good to merge but depending on when a release with this is needed, we may need to package a separate release with this change.

Got it! As this PR depends on the build fix implemented in #211, I will add that fix here, merge this PR and fix the conflicts in #211 so you guys can merge it whenever you want. Then I can create a new release-2.0 branch with only this PR on top of v2.0.0, release a new v2.1.0 from there and publish it in the Marketplace. Then you can follow your usual release schedule for the next ones, if that makes sense.