add missing any/none waiter error matching

[lucix-aws]

Adds missing functionality defined in the waiters spec:

error: A string representing the parsed AWS error code when looking for a specific error code, or boolean true to match on any error code, or boolean false to test if no errors were encountered.

Nothing actually uses this right now but I modified dynamodb's two error-match waiters with expected booleans to test generation.

[Madrigal]

So this is the actual change on behavior, returning true when there's any error even if we don't have a matcher for it?

[lucix-aws]

No, this is an explicitly configured matcher saying "retry if there's any error".

[Madrigal]

got it, where do we actually verify the new behavior then? We setup matchers, we verify we didn't get any error and that we only tried the expected amount of times, but I'm not sure where on these tests we check for the newly added boolean error

[lucix-aws]

TestWaiterRetryAnyError (this one) is configured to say "retry on any error" - so that tests the positive / true case - demonstrated by the first two mocked requests resulting in a retry.

Then TestWaiterSuccessNoError just says "immediately succeed on no error" - the negative / false case - demonstrated by the very first mocked response terminating in success.