Add a tag filtering mechanism to the plugin page

[schultzp2020]

Background

Currently the plugin page displays all plugins regardless of the plugin role specified in its package.json. e.g. 3scale-backend

Enhancement

• Instead of using the role property, add a tags property in the plugin's package.json. This is because the role property is not easily understandable i.e. a custom action has a role of backend-plugin-module
• Create a tag filtering mechanism based on the plugin role
• Create a search bar based on the plugin name and tags

[serenamarie125]

Acceptance Criteria:

1. remove "Learn more" link
2. make the description left aligned
3. add tags to the bottom of the card, have them left-aligned

Tags should include:

1. Frontend
2. Backend
3. Custom Actions

[gorkem]

One correction, If role refer to the backstage.role on package.json. We can not add tags instead of role but in addition to role. As backstage.role has significance to backstage build process.

[schultzp2020]

One correction, If role refer to the backstage.role on package.json. We can not add tags instead of role but in addition to role. As backstage.role has significance to backstage build process.

Whoops, maybe I should've clarified that. I was not planning on removing the role property.

[tumido]

Updating with a chat convo on this:

@christophe-f:

We could just add the tag in the PLUGINS_LIST constant. That will avoid to syncup and read all the package.json files, and add website specific content into the plugins (edited)

@tumido:

That makes sense... and it's not like tags for a plugin are gonna change anyways...

@schultzp2020:

So should we add the tags here? https://github.com/janus-idp/janus-idp.github.io/blob/main/apps/website/content/plugin-list.js#L19-L27

@christophe-f:

yes that would be much easier.

[AayushSaini101]

@schultzp2020 Can I work on this issue?

[schultzp2020]

@AayushSaini101 sorry, there is already an existing pr to fix this issue.