Move TIdAntiFreeze into its own runtime package

[rlebeau]

Right now, TIdAntiFreeze is implemented in the dclIndyCore design-time package, which is wrong, and requires some hacks to work. It should be in a run-time package instead. To avoid linking to it unnecessarily, it should be in its own separate run-time package. That way, users can choose whether to link to it, or even whether to install it at all.

[czhower]

The original design is that during run time it was to be linked in only and no pkg to avoid polluting the run time pkg with refs to the UI units. Maybe it has changed, but it used to work just fine by having it link in as a dcu.

[rlebeau]

The problem is that IdAntiFreeze.pas is included in the dclIndyCore package, which is a design-time package, so dropping a TIdAntiFreeze on a Form at design-time causes that package to be linked, which is not allowed. Certainly if a runtime project simply uses the IdAniFreeze.pas unit directly, and linked to the .DCU file, that would be fine, but then design-time support would be lost. And then there is C++Builder support to consider. Regardless of the intended goal, the current design is flawed, and has been for years. Moving TIdAntiFreeze to its own runtime package that is registered at design-time and linkable at runtime would solve all of these problems, and it is just correct component design in general.