RFC - Move Sharepoint Site profile from bundled to optional

[AliveDevil]

Seeing confusion internally, where people see "Sharepoint" and "Sharepoint Site", and immediately start to use the Sharepoint Site-profile.

This is in multiple ways not ideal, as the Site-profile is heavily limited in its practical use, outside of working around Microsoft Graph-behavior.

• The Sharepoint-profile doesn't require an explicit hostname to be configured.
• The Sharepoint Site-profile has to be configured in a specific way ("Web URL of Site" in Sharepoint Admin-panel, e.g. /sites/sitename)
  This path cannot point to anything different than a site.

Sharepoint has following naming schemes, which all are valid, and indistinguishable from a pure analysis view point:

• /sites/SiteName/SubSiteName/SubSiteName
• /teams/SiteName
• /SiteName
• /Sites/SiteName/LibraryName/
• /LibraryName
• /SiteName/LibraryName

There is no way to differentiate "/Sites/SiteName/SubSite" from "/Sites/SiteName/LibraryName".

To get to the drive content, this would be needed:

• /v1.0/sites/tenant.sharepoint.com:/Sites/SiteName/SubSite:/drive
  the other
• /v1.0/sites/tenant.sharepoint.com:/Sites/SiteName:/drives:/LibraryName
  Except, that this request is invalid, as there is no endpoint for sites/siteid/drives/driveid
  Thus the correct order here would be:
  • /v1.0/sites/tenant.sharepoint.com:/Sites/SiteName:/drives - find drive where name equals LibraryName
  • /v1.0/drives/<found drive id>

Proposal
Remove the Sharepoint Site-profile out of the default bundled profiles, and make is optional by making it installable through the Profiles-tab and refer to that profile, if all else fails.

// #14867