Add parenthesized flag to ExprTuple and ExprGenerator

[MichaReiser]

Summary

This PR adds an parenthesized prop to ExprTuple and ExprGenerator that expose if the tuple/genrator is parenthesized in the source.

The information is useful during linting and formatting, and dedecting if a tuple is parenthesized is somewhat involved.

Should this information be present in the AST: IMO, properties that are needed more than once are worth tracking in the AST, even if they don't have any semantical meaning.
It also simplifies implementing the new parser where it otherwise would need to be necessary to track the information separately.

Test Plan

I added new tests and reviewed the snapshot changes

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

ℹ️ ecosystem check encountered format errors. (no format changes; 1 project error)

openai/openai-cookbook (error)

warning: Detected debug build without --no-cache.
error: Failed to read examples/How_to_handle_rate_limits.ipynb: Expected a Jupyter Notebook, which must be internally stored as JSON, but this file isn't valid JSON: trailing comma at line 47 column 4

Formatter (preview)

ℹ️ ecosystem check encountered format errors. (no format changes; 1 project error)

openai/openai-cookbook (error)

ruff format --preview

warning: Detected debug build without --no-cache.
error: Failed to read examples/How_to_handle_rate_limits.ipynb: Expected a Jupyter Notebook, which must be internally stored as JSON, but this file isn't valid JSON: trailing comma at line 47 column 4

[charliermarsh]

If we track this for tuples, should we also track it for generators, where it's also optional?

[charliermarsh]

I def support this. I think I tried to pitch it at one point but there wasn't enough interest 😂