feat: add client pack and local pack rule

[SettingDust]

No description provided.

[juraj-hrivnak]

Sorry for the late response. Thanks for the PR.

I am not a fan of registering the export profiles like this:

val registry = mutableMapOf<String, (LockFile, ConfigFile) -> ExportProfile>()

init
{
    registry[ClientPackProfile.NAME] = { _, _ -> ClientPackProfile() }
    registry[CombinedPackProfile.NAME] = { _, _ -> CombinedPackProfile() }
    registry[ServerPackProfile.NAME] = { _, _ -> ServerPackProfile() }
    registry[CurseForgeProfile.NAME] = { lockFile, configFile -> CurseForgeProfile(lockFile, configFile) }
    registry[ModrinthProfile.NAME] = { lockFile, configFile -> ModrinthProfile(lockFile, configFile) }
}

A registry is not a bad idea indeed, but registering should be implemented differently.
How I would do it:

// exportProfile is a function that will create an ExportProfile and add it to the "registry".
exportProfile(name = "serverpack")( // A curried function that can accept ExportRules as varargs
    ServerPackRule()
)

[juraj-hrivnak]

With the things that I said, these companion objects become unnecessary.

[juraj-hrivnak]

I am closing this because I introduced a new DSL for creating export profiles, and this will likely be superseded by the scripting support.