[noissue]: Update pygtrie requirement from ~=2.4.2 to ~=2.5.0

[dependabot]

Updates the requirements on pygtrie to permit the latest version.

Changelog

Sourced from pygtrie's changelog.

Version History

2.5: 2022/07/16

• Add :func:pygtrie.Trie.merge method which merges structures of two tries.

• Add :func:pygtrie.Trie.strictly_equals method which compares two tries with stricter rules than regular equality operator. It’s not sufficient that keys and values are the same but the structure of the tries must be the same as well. For example:

  >>> t0 = StringTrie({'foo/bar.baz': 42}, separator='/')
  >>> t1 = StringTrie({'foo/bar.baz': 42}, separator='.')
  >>> t0 == t1
  True
  >>> t0.strictly_equals(t1)
  False
  

• Fix :func:pygtrie.Trie.__eq__ implementation such that key values are taken into consideration rather than just looking at trie structure. To see what this means it’s best to look at a few examples. Firstly:

  >>> t0 = StringTrie({'foo/bar': 42}, separator='/')
  >>> t1 = StringTrie({'foo.bar': 42}, separator='.')
  >>> t0 == t1
  False
  

  This used to be true since the two tries have the same node structure. However, as far as Mapping interface is concerned, they use different keys, i.e. ```set(t0) != set(t1)``. Secondly:

  >>> t0 = StringTrie({'foo/bar.baz': 42}, separator='/')
  >>> t1 = StringTrie({'foo/bar.baz': 42}, separator='.')
  >>> t0 == t1
  True
  

  This used to be false since the two tries have different node structures (the first one splits key into ('foo', 'bar.baz') while the second into ('foo/bar', 'baz')). However, their keys are the same, i.e. ```set(t0) == set(t1)``. And lastly:

  >>> t0 = Trie({'foo': 42})
  >>> t1 = CharTrie({'foo': 42})
  >>> t0 == t1
  False
  

  This used to be true since the two tries have the same node

... (truncated)

Commits

• 1587471 Prepare 2.5.0 release.
• 913f103 Introduce Trie.strictly_equals method
• 0bfda80 Tiny fix to eq implementation
• 29c16e5 Replace ‘_sorted’ by ‘_iteritems’ which stores the callback directly
• 8178b3c Add merge method
• c2611e8 Fix super() invocation for Python 2.7 compatibility
• d30106f Fix eq implementation by taking key into consideration
• a278a0c Minor fixes to issues with version-history.rst reported by Sphinx
• 2b11e09 Test all supported pickle protocol versions in e2e pickle test
• afc0a2d Fix new lint warnings; also enable a few more of the existing ones
• See full diff in compare view

You can trigger a rebase of this PR 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 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.