feat: validateBooleanMiddleware for controllers

[TarikGul]

Summary

This adds validation for boolean middleware inputs. It checks specifically for true, and false for known query params that expect booleans. It will error with a 400 BadRequest. For query params that are not part of the API, as normal we just ignore them as the API should not handle those query params.

Extra

I cleaned up the validation tests and utils for both validateBoolean and validateAddress by creating a util folder that handles that functionality.

closes: #398

[niklasad1]

I guess this is the idiomatic way of checking the queryParams, a bit annoying but fair enough.

[jsdw]

I guess it's because all query params are strings.

Maybe worth doing queryParamVal.toLowerCase() to support eg TRUE or True? Not too bothered though; nothing wrong with being strict and accepting only true or false.

In some apps, the mere presence or absense of a query param sets it to true or false, eg ?foo&bar leads to foo and bar being true. Again, I'm happy if we just want to be stirct and support only =true or =false; just throwing it out there :)

[TarikGul]

Maybe worth doing queryParamVal.toLowerCase() to support eg TRUE or True? Not too bothered though; nothing wrong with being strict and accepting only true or false.

I actually already set queryParamVal to lower case above.

[jsdw]

Oh yeah; apologies; I somehow missed that entirely :)

[jsdw]

If you wanted to save a few characters you could do ...queryParams: string[] here (if i recall the spread syntax properly) to avoid needing array parens anywhere... since it's just a manually built list anyway each time.

But not important at all!

[TarikGul]

I thought about this at first too actually and I think I settled with the explicit array because it makes it more clear.

[jsdw]

Love it; a huge improvement from the global list :)