Update zeitwerk requirement from >= 2.6.0, < 2.7.2 to >= 2.6.0, < 2.7.3

[dependabot]

Updates the requirements on zeitwerk to permit the latest version.

Changelog

Sourced from zeitwerk's changelog.

2.7.2 (18 February 2025)

• Internal improvements and micro-optimizations.

• Add stable TruffleRuby to CI.

2.7.1 (19 October 2024)

• Micro-optimization in a hot path.

• Raises Zeitwerk::Error if an autoloaded constant expected to represent a namespace does not store a class or module object.

• Adds truffleruby-head to CI, except for autoloading thread-safety (see why in oracle/truffleruby#2431).

2.7.0 (11 October 2024)

• Explicit namespaces can now also be defined using constant assignments.

  While constant assignments like

  # coordinates.rb
  Coordinates = Data.define(:x, :y)

  worked for most objects, they did not for classes and modules that were also namespaces (i.e., those defined by a file and matching subdirectories). In such cases, their child constants could not be autoloaded.

  This limitation has been removed.

• TracePoint is no longer used.

• Requires Ruby 3.2 or later.

  Gems that work with previous versions of Zeitwerk also work with this one. If they support Ruby versions older than 3.2 they can specify a relaxed version constraint for Zeitwerk like "~> 2.6", for example.

  In client projects, Bundler takes the Ruby requirement into account when resolving dependencies, so Gemfile.lock will get one compatible with the Ruby version being used.

2.6.18 (2 September 2024)

• Fixes a bug in which projects reopening the main namespace of a gem dependency

... (truncated)

Commits

• 6aa2821 Ready for 2.7.2
• 632f2bb Let get_or_set evaluate the fallback lazily
• b37c6d1 Add a couple more of tests
• d61c3e1 Define get_or_set for cref maps
• cc7d546 Revises some signatures
• 245fc05 Fixes signature annotation
• c3eaacc Adds a test for cref maps
• 177ab23 Docs improvements
• 85a9b97 Adds code comments
• c74ddf7 Introduce Zeitwerk::Cref::Map
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)