Split configuration by responsibility and tighten public value types

[HituziANDO]

Problem

SwiftyUpdateKitConfig combines identity, networking, comparison, presentation strings, retry settings, and storage environment in one long initializer. Some public types are also wider than needed: logs accept Any, successful version values remain optional, and condition protocols unnecessarily require reference types.

Scope

• Group app identity, network policy, and built-in presentation content into focused value types.
• Use non-optional UpdateInfo values for successful results.
• Change the logger contract to accept String.
• Remove AnyObject from condition protocols unless identity is required.
• Provide compatibility initializers and adapters with a documented deprecation schedule.

Dependencies

• Extract UpdateCheckService and add a structured async API #23

Acceptance criteria

• Networking code does not receive UI or storage settings it does not use.
• Successful callbacks do not require callers to unwrap guaranteed values.
• Value-type scheduling policies are supported.
• Existing valid initialization code has a clear migration path.

Tests

• Add compile-time API fixtures for old and new initialization paths and unit tests for configuration mapping.

Relevant files

• Framework/Sources/SwiftyUpdateKitConfig.swift
• Framework/Sources/Log.swift
• Framework/Sources/SUK.swift
• Framework/Sources/VersionCheckCondition.swift
• Framework/Sources/RequestReviewCondition.swift
• README.md