Add support for dry-run

[michaeldmitry]

Fixes #73

Solution

Add a dry_run optional argument to patch, replace, create, delete, delete_collection for AsyncClient and Client that will pass a dryRun query parameter to requests.
Additionally, fixed some linting :)

Context

Dry-running a request would be a nice addition (and a lightweight one too!) for users to perform validation calls to their spec changes that are not strictly typed by lightkube (e.g: resources limits and requests are dicts and are prone to invalid values like {"CpU": "-100km"})

[ca-scribner]

hey @gtsystem how do you feel about this? afaict it addresses all the points raised in #42, which was abandoned. I haven't manually tested it but at least the concept makes sense. wdyt?

[gtsystem]

No concern regarding the new feature. However it's hard to review as the styling changes add a lot of noise. @michaeldmitry can you isolate styling changes and actual feature in separate commits?

Also it would be good to know what tool are you using for styling and if there is any special configuration

[michaeldmitry]

@gtsystem separated (as much as possible) formatting and feature changes into 2 commits.
black version 24.8.0 is used for formatting with no special config.

BTW, should I bump the version in setup.py?

[gtsystem]

@gtsystem separated (as much as possible) formatting and feature changes into 2 commits. black version 24.8.0 is used for formatting with no special config.

Looks good.

BTW, should I bump the version in setup.py?

Yes, please

[michaeldmitry]

@gtsystem separated (as much as possible) formatting and feature changes into 2 commits. black version 24.8.0 is used for formatting with no special config.

Looks good.

BTW, should I bump the version in setup.py?

Yes, please

Done :)