Validate that query literal do not conflict with query params

[sugmanue]

Issue #, if available:

Description of changes:

Validate that query literal do not conflict with query params. Currently is possible to define a model like the following, that defines code as a query literal in the URI part of the @http trait and also the same query param in the OperationOneShape. This change will disallow this model that is not valid in practice.

$version: "2"
namespace smithy.example

// OperationOne defines a query literal `code` that conflicts with the
// query param defined in the input structure.

service SmithyExample {
    operations: [
        OperationOne
    ]
}

@http(code: 200, method: "GET", uri: "/example?code")
@readonly
operation OperationOne {
    input: OperationOneInput
    output: OperationOneOutput
}

structure OperationOneInput {
    @httpQuery("code")
    code: String

    @httpQuery("state")
    state: String
}

structure OperationOneOutput {
    @required
    @httpHeader("Content-Type")
    contentType: String

    @required
    @httpPayload
    content: Blob
}