Remove redundant fga_client.close in python

[davidroeca]

Description

fga_client.close() is handled by the context manager so it isn't needed, as discussed in openfga/python-sdk#191

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

[linux-foundation-easycla]

• ❌ - login: @davidroeca / name: David Roeca . The commit (6826e93) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[davidroeca]

Please hold off on review. I'm realizing I still need to factor in changes from #116

[dyeam0]

Please hold off on review. I'm realizing I still need to factor in changes from #116

Hi @davidroeca. While your refactoring and this PR is on hold, can you change it to Draft PR state? That helps with our tracking and makes the status more accurate. Thanks!

[davidroeca]

Hi @dyeam0 that makes sense to me, but unfortunately I don't see a way to do so

[rhamzeh]

@davidroeca (for next time) it's from the side bar

I marked it as draft for now - let us know when you believe is ready to review.

Also please make sure to sign the Linux Foundation's CLA (#545 (comment)) when you are ready for it to be merged. It's a one time process, and without it we're restricted from merging.

[curfew-marathon]

This PR has had no human activity for 90 days, so it has been marked lifecycle/stale.

This is automated backlog grooming, not a judgment on the work.

What happens next, unless there is activity:

• In 30 days, it will move to lifecycle/closing-soon
• 30 days after that, it will be closed

To keep it open, push a commit or leave a comment, and the clock will reset. For work that should not auto-close, such as an RFC or long-running experiment, ask a maintainer to add lifecycle/frozen.

[curfew-marathon]

This PR has had no human activity for 30 days since being marked lifecycle/stale, so it has now been marked lifecycle/closing-soon.

It will be closed in 30 days unless there is new activity.

If the work still matters, this is the moment to say so: leave a comment, push a commit, or ask a maintainer to add lifecycle/frozen if it should be kept open long-term.

If this work is no longer being pursued, no action is needed.