[fix] Add `RestrictionComments` to `CustomsInfo` Create parameter set

[nwithan8]

Description

Adds RestrictionComments parameter to the CustomsInfo.Create parameter set, and enforces its presence based on the value of RestrictionType (RestrictionComments must be set if RestrictionType is set (not null) and is anything other than "none")

Closes #597

Adds expanded TopLevelRequestParameterDependentsAttribute and NestedRequestParameterDependentsAttribute to accommodate for mix of value- and presence-based independent-dependent relationships. New possible enforcements, e.g.:

• Parameter B must (not) be set if Parameter A is (not) a certain value
• Parameter B must (not) be a certain value if Parameter A is (not) set

Testing

• Add unit tests to confirm inter-dependency Parameter checks
• Add unit test to confirm RestrictionComments validation based on RestrictionType
• Update test fixtures accordingly
• Re-record cassettes as needed

Pull Request Type

Please select the option(s) that are relevant to this PR.

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Improvement (fixing a typo, updating readme, renaming a variable name, etc)

[nwithan8]

Huh, ya learn something new every day. I've never seen these customs values used in the wild.

I'm seeing some unrelated cassettes re-recorded here, were they expired? I'd recommend not including unrelated cassette changes if we can avoid it.

This kind of ballooned out, as the CustomsInfo fixture affected Shipment fixtures, which affects a lot of cassettes.