We found this same issue occurs with one small change to the aforementioned setup. Move the Objective-C class to the Swift Package -- in an ObjC target that depends on the Swift target.
You will hit the same error in your Xcode project as before. Unfortunately, the module map solution does not seem to fix this case.