Move profile and ruletype logic out of engine package

[dmjb]

A bunch of profile and rule type logic lives in the engine package. This PR moves those functions into the profiles and ruletypes packages.

This avoids circular dependencies in a future PR, and also groups logic for specific domain concepts in their own packages.

Summary

Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.

Fixes #(related issue)

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[dmjb]

The use of this type was leading to a circular dependency, and after reviewing the code - it appears it is only used to pass around a single value. Instead of fixing the circular dependency, I just removed the use of this type here.

[coveralls]

coverage: 52.691% (+0.03%) from 52.662%
when pulling 508380b on move-functions-from-engine
into e9e43e9 on main.