ResourceOperationInputOutput errors if a nested resource only has a list operation

[tlindsay42]

Consistently getting the following error for all resource properties when I attempt to create a nested resource with only a list operation that references all of the nested resource properties in a structure used by a list. If I add a get operation referencing the resource properties in an output structure, the errors clear.

──  ERROR  ──────────────────────────────────────── ResourceOperationInputOutput
Shape: com.example#NamespaceTaskResource
File:  [redacted]/model/namespace/task/namespace-task.smithy:8:1

7| @since("2025-10-09")
8| resource NamespaceTaskResource {
 | ^

Resource property `Name` is not used in the input or output of create or an
instance operation.

[JordonPhillips]

I've been looking into this. I agree that we should be inspecting lists for this. It turns out this a more wide-spread issue though - we seem to not consider properties bound to the output list to be bound at all, for any purpose. The same is true for identifiers. There is some subtlety to differentiating between instance bindings and collection bindings, but we should be able to get something together