Add extensions to register conditions in the Rules module

[MikeAlhayek]

Here is a summary of the changes:

• Added new OrchardCore.Rules.Core project.
• Added the new AddRule<> extensions in the Core project
• Cleaned up the OrchardCore.Rules project by using the new extensions.

[hishamco]

This is not breaking

It's a binary-breaking change

[MikeAlhayek]

@hishamco
OC.Rules depends on OC.Rules.Core so if someone already depend on OC.Rules, they they'll have access to everything in OC.Rules.Core so it won't have any compile or run time errors. So it should not be breaking anyone

[hishamco]

OC.Rules.Core so it won't have any compile or run time errors.

I know what you mean, but while you changed the assembly it was considered a binary breaking change, anyhow while we accept the breaking changes in minor releases it's not a problem

Again can we prevent breaking changes in minor releases coz sometimes accept and sometimes not :)

[MikeAlhayek]

@hishamco the only thing that would break is moving the rules to a different project because YesSQL stores the assembly name in the database when it is stored. So I am moving the models back to make sure Yessql won't have serialization problem.