Fix codegen to ignore httpLabel on non-input shapes per Smithy spec

[RanVaknin]

Per the Smithy spec, httpLabel on non-input shapes "has no meaning and is simply ignored." However, AddShapes.findRequestUri() was throwing a ModelInvalidException when it found a shape with a URI bound member that wasn't a direct operation input.

When the shape isn't a direct operation input, it now returns empty instead of throwing (results in codegen ignoring this member). The existing validation for operations with a missing requestUri is unchanged.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[joviegas]

How does generated code looks like when we have below

  "NestedOptions": {
      "type": "structure",
      "members": {
        "pageSize": {
          "shape": "String",
          "location": "uri",
          "locationName": "pageSize"
        }
      }
    }

when we say

httpLabel is only considered when applied to top-level members of an operation's input structure. This trait has no meaning in any other context and is simply ignored.

what does ignore mean ? should we internally treat it as

  "NestedOptions": {
      "type": "structure",
      "members": {
        "pageSize": {
          "shape": "String",
          "locationName": "pageSize"
        }
      }
    }

and marshall it in the regular payload. , just as we do for shapes where locationName is not specified

Or completely remove pageSize from NestedOptions structure ?

Can we please have a test case comparing a generated code ?