fix: relaxed marshmallow requirement to see if conflicts arise

[allisonsuarez]

Summary of Changes

CI marshmallow incompatible version conflicts.

Tests

What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line

Documentation

What documentation did you add or modify and why? Add any relevant links then remove this line

CheckList

Make sure you have checked all steps below to ensure a timely review.

• PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.
• PR includes a summary of changes, including screenshots of any UI changes.
• PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public python functions and the classes in the PR contain docstrings that explain what it does
• PR passes all tests documented in the developer guide

[Golodhros]

LGTM

Thanks for doing this!

[feng-tao]

it seems marshmallow-annotations needs to change to range as well

[feng-tao]

thanks @allisonsuarez for the quick fix!