Cashtab runs every input address string through the parseAddressForParams function -- the function is where the logic for "does this address even have params?" exists.

So, a normal address with no params will return the above object.

kind of a catch 22 here.

The available methods to check on duplicate keys also involve iterating over everything, which we already need to do to parse the individual params.

So, we can use bools -- which adds lots of flags, but catches duplicates during the iteration that needs to happen anyway.

Or we can do it up front -- which simplifies the code but does double up on iterations. I'm not sure if the new Set() approach is better or worse than alt approaches. I didn't want to have a function that is just doing a for loop before the for loop.