WIP : Merge "Access to the list of all questions tracked"

Description

Adds a page with all the questions followed by a user

Migration and compatibility

• The merge request updates the models, as a consequences, database migrations are needed.
• The merge request breaks the compatibility.

TODO

Before being accepted, any merge request must fulfill the following requirements:

• Check PEP8 writing style as described in CONTRIBUTING.md.
• Ensure existing tests are still working properly.
• Features have been tested.
• Every translatable strings are written in proper english.
• Every translatable strings are tagged for translation using gettext, blocktrans and/or trans.
• Ensure that there is no side effect in files: changes are only related to one, and only one feature.
• Ensure that no file has been removed by accident.
• API is documented, as well as the behavior, if needed, in docs.
• Ensure the commit history is “clean enough” (this means no extra merge commits, etc).
• Ensure pipeline succeeds.

Deploy Notes

• Add a new page with all the questions followed by a user
• Add an acces to this page on the home page

Steps to Test or Reproduce

On the home page, in the topic Asking for access to the page of the following questions The page lists the questions followed concerning courses, activities and resources. At the moment the agora is propagated only to the question on courses

git pull --prune
git checkout agora

Impacted Areas in Application

Affects homepage design

Closes #40 (closed)