feat: update definitions to support ABAC Conditions

[jpadilla]

Description

NOTE: this PR targets a new branch feat/abac

• ListObjectsRequest now accepts context
• StreamedListObjectsRequest now accepts context
• WriteAuthorizationModelRequest now accepts conditions
• CheckRequest now accepts context
• ExpandRequest stops accepting user

References

Review Checklist

• I have clicked on "allow edits by maintainers".
• I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
• The correct base branch is being used, if not main
• I have added tests to validate that the change in functionality is working as expected

[rhamzeh]

We're keeping any?

[miparnisari]

If in the future we'll introduce it, it makes sense to have it here so that we reserve the field number

[miparnisari]

Here and elsewhere in this PR: why do we need this? seems redundant. In the past, we removed these two: see #4

Whenever we have a mix of min_len/max_len and pattern validation, remove the min_len and max_len in favor of an updated pattern that includes the length.

[jpadilla]

thinking is that the error returned in the case that length isn't within constraints is better value length must be between 1 and 50 runes, inclusive as opposed to value does not match regex pattern. It is redundant and likely a slight performance hit, I'll remove for now.