Move all generic macros to XWiki/Macros location

[snazare]

Following #277 and #287 here is the current structure of Pro Macros :

I. In the Confluence/Macros location:

1. Confluence bridge macros prefixed with 'confluence_' and not used as standalone macros after the migration: [in pro-macros-confluence-bridges module]

• attachments - same content available in default attachments tab
• balsamiq - old xwiki integration existed. We should improve that one if requested.
• children - existing xwiki native macro
• column - formatting macro to be used with section macro
• contentbylabel - uses cql parser
• details - also called pageproperties - uses cql parser - XWiki's native AWM is a better option for the same functional result
• detailssummary - also called pagepropertiesreport - uses cql parser, used with details macro - XWiki's native AWM is a better option for the same functional result
• drawio - existing xwiki native diagram app
• gallery - existing xwiki native macro
• gliffy - existing xwiki native diagram app
• layout - formatting macro useful for importing Confluence content in the same structure
• layout-cell - formatting macro useful for importing Confluence content in the same structure
• layout-section - formatting macro useful for importing Confluence content in the same structure
• mathblock - existing mathjax xwiki macro
• mathblock-ref - existing mathjax xwiki macro
• mathinline - existing mathjax macro
• mockup - existing xwiki native diagram app
• multimedia - existing xwiki native functionality
• note - existing xwiki native functionality - formatting boxes or panel should be used
• pagetree - existing xwiki native documenttree macro
• paste code - existing xwiki native code macros
• section - formatting macro to be used with column macro
• time - existing xwiki native date macro
• tip - existing xwiki native success macro
• wireframe - old xwiki integration existed. We should improve that one if requested.

2. Confluence macros not prefixed, that can be used standalone after migration: [in pro-macros-ui module]

• content report table
• contributors
• excerpt
• excerpt-include (java macro)
• expand
• profile-picture
• recently-updated
• userlister
• userProfile (java macro)
• view-file

3. Legacy Confluence bridges that were not prefixed when created and that should not be used after the migration (we maintain them for backwards compatibility for users that migrated a while ago): [in pro-macros-confluence-bridges module]

• anchor - existing xwiki native "id" macro, we already convert it to id during conversions
• net-presago-stream-macro - legacy microsoft stream
• viewfile - converted into view-file
• viewxls - converted into view-file
• viewppt - converted into view-file
• viewdoc - converted into view-file
• viewpdf - converted into view-file
• time - with datetime parameter

II. In the XWiki/Macros location: [in pro-macros-ui module]

• button - customizable button
• msStream
• panel - customizable panel, similar to formatting boxes
• status - highlighted text
• team - shows team members in circles

Proposal:

After gathering feedback from our users and considering the new organization of the macros in Confluence migration specific and generic, I would propose the following changes:

Macro	New location	New module	Reason
content-report-table	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.
contributors	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.
excerpt	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.
excerpt-include	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned. We need a documentation page in XWiki/Macros too.
expand	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.
profile-picture	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.
recently-updated	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.
userProfile	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned. We need a documentation page in XWiki/Macros too.
view-file	XWiki/Macros		XWiki/Macros is a more appropriate location for generic pro macros compared to Confluence/Macros. If non Confluence-migration users install the generic Pro Macros module and see "Confluence" in their navigation they may be confused and concerned.