@preconcurrency import unexpectedly affected by order

[stevapple]

Description
@preconcurrency import should apply @preconcurreny to what it imports exactly. eg., @preconcurrency import struct Foundation.Date should import exactly Foundation.Date as a @preconcurreny struct.

However, an experiment found that the compiler will emit false diagnostic on @preconcurrency import if there're more than one imports for the same module and the @preconcurrency one is not the first of them.

Steps to reproduce

import struct Foundation.Data
@preconcurrency import struct Foundation.Date

struct DateWrapper: Sendable {
    let date: Date
}

triggers compiler warning

bug.swift:5:9: warning: stored property 'date' of 'Sendable'-conforming struct 'DateWrapper' has non-sendable type 'Date'
    let date: Date
        ^
Foundation.Date:1:15: note: struct 'Date' does not conform to the 'Sendable' protocol
public struct Date : ReferenceConvertible, Comparable, Equatable {
              ^
bug.swift:1:1: remark: add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'Foundation'
import struct Foundation.Data
^
@preconcurrency 
bug.swift:2:17: remark: '@preconcurrency' attribute on module 'Foundation' is unused
@preconcurrency import struct Foundation.Date
~~~~~~~~~~~~~~~~^

Expected behavior
The code should compile without warnings.

Environment
Swift version 5.7.3 (swift-5.7.3-RELEASE)
Target: x86_64-unknown-linux-gnu

Additional context
If we change the order of the two imports in the example code:

@preconcurrency import struct Foundation.Date
import struct Foundation.Data

struct DateWrapper: Sendable {
    let date: Date
}

Then it is warning-free as expected😅

[DougGregor]

The ordering issue is addressed by #74413, but we're still not modeling the import of specific entities (i.e., an import struct).