Fixed email change modal

Fixes to research outputs display

Multiple fixes on Other type research outputs are saved & displayed

Removed console.log

Optimized note creation, update and archive

Added resize button in tinymce editors

Fixes on tinymce editors loading for performance purpose

Fixed required field display when adding a new dataset

Added default research output type when creating the plan

Removed Cancel Edit Button & Other Type should be cleaned when ading a new research output

Adding a new research output should display inputs not values

Removed console.log

Added edition button on research ouput form

Merged DMPRoadmap V2.1.2

Added selectable ResearchOutput Type to ResearchOutput form

Datasets has been renamed as Research outputs

Moved datasets form to its own tab

User have now to click on a button to change the plan visibility

Added plan creation from copied link

Added collapsible example answers

Fix for editor autoresize

users should be able to choose which dataset to export

Added Datasets support for answers comments

Fixed common answers checkbox, should only block dataset in the current section

Fixed answers display for each dataset in phase edition

Datasets integration

Users can now choose one or multiple phases when exporting a plan

Disabled eslint for cookie banner

Solved issue with tinymce toolbar options

Updated Usage page display to fix several issues. ...

- Moved mouse pointer instruction.
    - Made textual changes to "No. of plans by template"
    - The bar charts for  "No. users joined during last year" and
    "No. plans during last year" months are in ascending order. They were
    in descending order previously. Updated the count statistics methods
    in statistics_controller.rb.
    - The "No. plans by template" bar chart is now  replaced by a stacked bar chart
    as this is visually better for large data.
    - updated the by_template method in the create_or_update.rb with code from @xsrust.
    This now aggregates template counts for a month correctly.

    Fix for issue #1679.