Remove all minimum/maximum and minLength/maxLength

[dmosorast]

Description of change

In a similar vein as #44, I would like to remove all of the restrictive properties from this schema so that the tap doesn't need to manually evolve in sync with the Chargebee API.

However, I don't have an account to test this (and I'm not familiar with the semantics of this data). So, I'd like to get someone familiar with the data and service, and ideally someone who can run the tap to confirm that it runs successfully with target-stitch if possible so that I can confirm that the Stitch Import API will accept actual records with the new schemas (to fix errors like in issue #43).

Manual QA steps

• Requesting community assistance.

Risks

• Unknown, needs investigated further.
• Anecdotally, these should make the schemas less restrictive, so it should be backwards compatible, but may not be semantically desired, as mentioned above.

Rollback steps

• revert this branch, release new patch version.

[dmosorast]

In a wonderful lesson about the need to run the code for all PRs, no matter how small, this and #44 have invalid JSON due to trailing commas left behind.

I can't update this PR right now, but it definitely suffers from the same problem.