[feat] Add missing options

[nwithan8]

Description

Add all missing shipping options.

NOTE: Some options are/continue to be the wrong type (e.g. string instead of bool, string instead of DateTime (#520)). This PR is purely additive, with only new options and documentation on existing options to point out where a type is invalid. We should consider fixing these in a breaking change in the future.

Closes #592

Testing

Pull Request Type

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

• Bug fix (non-breaking change which fixes an issue)
• 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)

[jchen293]

Why do some options have a type comment while others don't?

[jchen293]

Should the comment be any?

Suggested change

	public string? CarrierInsuranceAmount { get; set; } // number
	public string? CarrierInsuranceAmount { get; set; } // any

[nwithan8]

Why do some options have a type comment while others don't?

Those with comments are to denote options that are technically the wrong type (e.g. a "string" type, but server-side, it parses it as a number. An end-user could potentially provide a non-numeric string, which would cause issues server-side). These should be considered for changes during the next breaking changes release cycle.

[Justintime50]

As mentioned in the past, I don't believe exposing all available options is the right play. Many are intentionally undocumented for various reasons - many need to be vetted for validity. I would caution against moving forward with this PR and instead continue having users rely on the custom option override you built to allow passing options that may not be officially supported.