Change the OC package references to 1.8.0 instead of 1.8.2 (OSOE-846)

[sarahelsaig]

Based on @Piedone 's advice in OCC:

I think the OCC packages should always target the .0 minor version of the latest version; i.e., 1.8.0 in this case, so people can use the packages regardless of them being on 1.8.0, 1.8.1, 1.8.2, or 1.8.3 (currently they're forced to use at least 1.8.2). During development and testing though, we should use the very latest, if somehow this can be done.

This is not possible for the projects that use HL, specifically OrchardCore.Commerce.Inventory and OrchardCore.Commerce.ContentFields.

Once this is done, also update OCC's Directory.Packages.props as suggested here.

Jira issue

[Piedone]

This would require us to disable package consolidation checks for OC versions.

[Piedone]

So, we'd need to always update the consolidation check disable regex to the current baseline OC version, i.e. the one we use in all shared projects (not web projects). However, something like "2.1" is not really unique, so we risk missing actual consolidation errors too.

We could also extend dotnet-consolidate with an option to exclude projects or packages from consolidation by regex (the -e option can exclude packages, but you need to list them all; we can do that, but we'd need to generate a list of 190 OC packages).

[sarahelsaig]

It would be good to exclude the "main" (*.Web.csproj) project from consolidation since that's where all the custom project versions will reside. This may be done in GHA:

• Add an option to specify project file(s) to exclude
• Use dotnet sln solution.sln remove excluded.csproj to remove each excluded project from the solution file
• Run dotnet-consolidate
• Use git reset --hard to restore the solution

[Piedone]

Hmm, interesting, indeed! We need to do this holistically, not in this project, so this instead: Lombiq/GitHub-Actions#354.