GeezerVison

Fixes #784.

Summary

Remove the assertion that Literal[[], []].__args__ is ([], []). python/cpython#153914 deliberately changed typing.Literal to deduplicate unhashable arguments, so Python 3.14.7 now returns ([],) instead. On supported Python versions where typing_extensions.Literal aliases typing.Literal, the old assertion therefore contradicts the standard library behavior.

This PR just deletes the assertion entirely: the behaviour here is now version-dependent, and the assertion was always testing an implementation detail that wasn't really that important.

Historical context

• The assertion entered typing_extensions in Fix various things with Literal #145. That PR addressed (🐞) Literal doesn't flatten it's arguments #113 and backported bpo-42345: Fix three issues with typing.Literal parameters cpython#23294 and bpo-42345: Fix hash implementation of typing.Literal cpython#23383. The assertion was copied verbatim with the rest of CPython's LiteralTests.test_args in the first commit of that PR. There was no discussion about this particular assertion on Fix various things with Literal #145.
• The original CPython behavior was intentional. In the original review discussion, a reviewer proposed deduplicating unhashable arguments as well. The PR author noted that changing the shared deduplication helper would slow down Union, and Guido asked whether mutable Literal arguments were actually valid.
• PEP 586 rejects mutable Literal arguments at type-checking time but intentionally does not validate them at runtime. The CPython reviewers therefore agreed not to deduplicate mutable arguments. Guido subsequently requested explicit __args__ coverage, and commit f653d680 introduced the exact assertion that Fix various things with Literal #145 later copied.
• gh-153896: Deduplicate unhashable Literal params cpython#153914 revisited that historical decision and now deduplicates unhashable arguments too; the change was backported to Python 3.13, 3.14, and 3.15. The old assertion is consequently obsolete and does not represent a typing_extensions implementation bug.