Fix CocoaPods build: guard KBHostArbiterHookObjC import with SWIFT_PACKAGE

Under CocoaPods, subspecs are merged into a single pod module, so there
is no standalone `KBHostArbiterHookObjC` Clang module to import. The
ObjC header is exposed via the pod's umbrella header. Guarding the
import with `#if SWIFT_PACKAGE` keeps SPM working while unblocking
CocoaPods consumers.

Bumps podspec to 1.0.1.

Fixes #1, #2.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Muskupecli

KeyboardHostBundleID.podspec

@@ -1,6 +1,6 @@
 Pod::Spec.new do |s|
   s.name             = 'KeyboardHostBundleID'
-  s.version          = '1.0.0'
+  s.version          = '1.0.1'
   s.summary          = 'Resolve the host app Bundle ID from an iOS custom keyboard extension (iOS 16 – iOS 26.4+).'
   s.description      = <<-DESC
     Drop-in library for iOS third-party keyboard extensions (UIInputViewController)

Sources/KeyboardHostBundleID/KeyboardHost.swift

@@ -9,7 +9,9 @@
 
 import UIKit
 import Foundation
+#if SWIFT_PACKAGE
 @_implementationOnly import KBHostArbiterHookObjC
+#endif
 
 /// Public API for resolving the host app's Bundle ID from inside a keyboard
 /// extension.