Add top level Multi Tenancy menu

[ns8482e]

Add top level Multi Tenancy menu and Move tenants and Tenant feature profile under Multi Tenancy menu

Fixes #12670

[MikeAlhayek]

@ns8482e
If you want to name it "Multi Tenancy", maybe it should be written "Multi-Tenancy". By what if you change the main menu to "Tenants" and then replace current "Tenants" with "Management" or "Manage Tenants"? So it would look like this

builder
    .Add(S["Tenants"], "after", tenants => tenants 
        .AddClass("tenants").Id("tenants")
        .Add(S["Manage"], S["Manage"].PrefixPosition(), manage => manage 
            .Action("Index", "Admin", new { area = "OrchardCore.Tenants" })
            .Permission(Permissions.ManageTenants)
            .LocalNav()
        )
    );

[Skrypt]

Moving the menu items makes sense to me. That's a top-level feature.

[ns8482e]

@MikeAlhayek I feel "Multi Tenancy" as top level menu as it represents a grouping of features related to multi-tenant, where as "Tenants" / "Tenant Features Profile" individual features, menu name kept it as is as we are used to with those menu names

[MikeAlhayek]

I understand. IMO, "Tenants" delivers the same meaning in a shorter manner. But either way, its up to you

[ns8482e]

Some other CMS refer that top level menu as "Sites"

[ns8482e]

I am fine to use any top level menu name all agrees to

[MikeAlhayek]

@ns8482e
Personally I think "Tenants" is better than "Sites" or "Multi-Tenancy". I'll leave to you and others.

[hishamco]

I also see the term Sites in some CMSs, it's more clear for non technical users

[sebastienros]

My suggestion

• Multi-Tenancy
  • Feature Profiles
  • Tenants (because we already call it this way everywhere)

[MikeAlhayek]

@ns8482e I make the changes @sebastienros mentioned. Feel free to merge this PR.

It may be a good idea to document the change in 1.7.0 release notes file.