Bump zeitwerk from 2.6.8 to 2.6.18

[dependabot]

Bumps zeitwerk from 2.6.8 to 2.6.18.

Changelog

Sourced from zeitwerk's changelog.

2.6.18 (2 September 2024)

• Fixes a bug in which projects reopening the main namespace of a gem dependency managed by its own Zeitwerk loader could not reload the constants they added to that external namespace.

2.6.17 (29 July 2024)

• Fix log message when eager loading a directory ends.

2.6.16 (15 June 2024)

• Logging prints a message when a directory that was not ignored is skipped anyway because it contains no Ruby files.

• Internal refactors.

2.6.15 (26 May 2024)

• Internal improvements.

2.6.14 (14 May 2024)

• Implements Zeitwerk::Loader#all_expected_cpaths, which returns a hash that maps the absolute paths of the files and directories managed by the receiver to their expected constant paths.

  Please, check its documentation for further details.

2.6.13 (6 February 2024)

• There is a new experimental null inflector that simply returns its input unchanged:

  loader.inflector = Zeitwerk::NullInflector.new

  Projects using this inflector are expected to define their constants in files and directories with names exactly matching them:

  User.rb       -> User
  HTMLParser.rb -> HTMLParser
  Admin/Role.rb -> Admin::Role
  

  Please see its documentation for further details.

... (truncated)

Commits

• f96c260 Ready for 2.6.18
• f9b21aa Fix autoload_path_set_by_me_for? with inceptions
• 8100bd1 Update project rules about crefs
• 1beae0c Ready for 2.6.17
• 9e3e043 Fix log message when eager loading a directory ends
• 4f285de Ready for 2.6.16
• b6f7015 Remove ruby-lsp from the Gemfile
• 4105648 Introduces the private class Zeitwerk::Cref
• 95f7c04 Add ruby-lsp to the Gemfile
• 756717b Merge pull request #295 from kianmeng/fix-typos
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.