Depends on OrchardCore.ContentFields.Core (OCC-434)

[infofromca]

Is your feature request related to a problem? Please describe

current OCC Projects depends on OrchardCore.ContentFields, with new OC, we should depends on OrchardCore.ContentFields.Core

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Jira issue

[sarahelsaig]

We actually use content fields in a lot of places and not just service implementations from OrchardCore.ContentFields.Core, so I'm not sure this is possible. We'd need a more thorough overview to see if there is viable.

Also, could you explain why such a basic dependency should be avoided? I think it's okay to assume that you will have content fields on a CMS website. Even if you are using a different front end I don't see OrchardCore.ContentFields as an overhead big enough to justify the added complexity of making it optional.

[hishamco]

@sarahelsaig, after my PR OrchardCMS/OrchardCore#18877, we can reference OrchardCore.ContentFields.Core instead to avoid module-to-module dependency