build(deps-dev): bump pyparsing from 3.0.9 to 3.1.1 (#22)

[//]: # (dependabot-start)
⚠️  **Dependabot is rebasing this PR** ⚠️ 

Rebasing might not happen immediately, so don't worry if this takes some
time.

Note: if you make any changes to this PR yourself, they will take
precedence over the rebase.

---

[//]: # (dependabot-end)

Bumps [pyparsing](https://github.com/pyparsing/pyparsing) from 3.0.9 to
3.1.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pyparsing/pyparsing/releases">pyparsing's
releases</a>.</em></p>
<blockquote>
<h2>Pyparsing 3.1.0a1</h2>
<p>NOTE: In the future release 3.2.0, use of many of the pre-PEP8
methods (such as <code>ParserElement.parseString</code>) will start to
raise <code>DeprecationWarnings</code>. 3.2.0 should get released some
time later in 2023. I currently plan to completely drop the pre-PEP8
methods in pyparsing 4.0, though we won't see that release until at
least late 2023 if not 2024. So there is plenty of time to convert
existing parsers to the new function names before the old functions are
completely removed. (Big help from Devin J. Pohly in structuring the
code to enable this peaceful transition.)</p>
<p>Version 3.2.0 will also discontinue support for Python versions 3.6
and 3.7.</p>
<ul>
<li>
<p>API ENHANCEMENT: <code>Optional(expr)</code> may now be written as
<code>expr | &quot;&quot;</code></p>
<p>This will make this code:</p>
<pre><code>&quot;{&quot; + Optional(Literal(&quot;A&quot;) |
Literal(&quot;a&quot;)) + &quot;}&quot;
</code></pre>
<p>writable as:</p>
<pre><code>&quot;{&quot; + (Literal(&quot;A&quot;) |
Literal(&quot;a&quot;) | &quot;&quot;) + &quot;}&quot;
</code></pre>
<p>Some related changes implemented as part of this work:</p>
<ul>
<li><code>Literal(&quot;&quot;)</code> now internally generates an
<code>Empty()</code> (and no longer raises an exception)</li>
<li><code>Empty</code> is now a subclass of <code>Literal</code></li>
</ul>
<p>Suggested by Antony Lee (issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/412">#412</a>),
PR (<a
href="https://redirect.github.com/pyparsing/pyparsing/issues/413">#413</a>)
by Devin J. Pohly.</p>
</li>
<li>
<p>Added new class property <code>identifier</code> to all Unicode set
classes in <code>pyparsing.unicode</code>, using the class's values for
<code>cls.identchars</code> and <code>cls.identbodychars</code>. Now
Unicode-aware parsers that formerly wrote:</p>
<pre><code>ppu = pyparsing.unicode
ident = Word(ppu.Greek.identchars, ppu.Greek.identbodychars)
</code></pre>
<p>can now write:</p>
<pre><code>ident = ppu.Greek.identifier
# or
# ident = ppu.Ελληνικά.identifier
</code></pre>
</li>
<li>
<p>Reworked <code>delimited_list</code> function into the new
<code>DelimitedList</code> class. <code>DelimitedList</code> has the
same constructor interface as <code>delimited_list</code>, and in this
release, <code>delimited_list</code> changes from a function to a
synonym for <code>DelimitedList</code>. <code>delimited_list</code> and
the older <code>delimitedList</code> method will be deprecated in a
future release, in favor of <code>DelimitedList</code>.</p>
</li>
<li>
<p>Added new class method <code>ParserElement.using_each</code>, to
simplify code that creates a sequence of <code>Literals</code>,
<code>Keywords</code>, or other <code>ParserElement</code>
subclasses.</p>
<p>For instance, to define suppressable punctuation, you would
previously write:</p>
<pre><code>LPAR, RPAR, LBRACE, RBRACE, SEMI = map(Suppress,
&quot;(){};&quot;)
</code></pre>
<p>You can now write:</p>
<pre><code>LPAR, RPAR, LBRACE, RBRACE, SEMI =
Suppress.using_each(&quot;(){};&quot;)
</code></pre>
<p><code>using_each</code> will also accept optional keyword args, which
it will pass through to the class initializer. Here is an expression for
single-letter variable names that might be used in an algebraic
expression:</p>
<pre><code>algebra_var = MatchFirst(
    Char.using_each(string.ascii_lowercase, as_keyword=True)
)
</code></pre>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/pyparsing/pyparsing/blob/master/CHANGES">pyparsing's
changelog</a>.</em></p>
<blockquote>
<h2>Version 3.1.1 - July, 2023</h2>
<ul>
<li>
<p>Fixed regression in Word(min), reported by Ricardo Coccioli, good
catch! (Issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/502">#502</a>)</p>
</li>
<li>
<p>Fixed bug in bad exception messages raised by Forward expressions. PR
submitted
by Kyle Sunden, thanks for your patience and collaboration on this (<a
href="https://redirect.github.com/pyparsing/pyparsing/issues/493">#493</a>).</p>
</li>
<li>
<p>Fixed regression in SkipTo, where ignored expressions were not
checked when looking
for the target expression. Reported by catcombo, Issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/500">#500</a>.</p>
</li>
<li>
<p>Fixed type annotation for enable_packrat, PR submitted by Mike
Urbach, thanks! (Issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/498">#498</a>)</p>
</li>
<li>
<p>Some general internal code cleanup. (Instigated by Michal Čihař,
Issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/488">#488</a>)</p>
</li>
</ul>
<h2>Version 3.1.0 - June, 2023</h2>
<ul>
<li>Added <code>tag_emitter.py</code> to examples. This example
demonstrates how to insert
tags into your parsed results that are not part of the original parsed
text.</li>
</ul>
<h2>Version 3.1.0b2 - May, 2023</h2>
<ul>
<li>
<p>Updated <code>create_diagram()</code> code to be compatible with
railroad-diagrams package
version 3.0. Fixes Issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/477">#477</a>
(railroad diagrams generated with black bars),
reported by Sam Morley-Short.</p>
</li>
<li>
<p>Fixed bug in <code>NotAny</code>, where parse actions on the negated
expr were not being run.
This could cause <code>NotAny</code> to incorrectly fail if the expr
would normally match,
but would fail to match if a condition used as a parse action returned
False.
Fixes Issue <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/482">#482</a>,
raised by byaka, thank you!</p>
</li>
<li>
<p>Fixed <code>create_diagram()</code> to accept keyword args, to be
passed through to the
<code>template.render()</code> method to generate the output HTML (PR
submitted by Aussie Schnore,
good catch!)</p>
</li>
<li>
<p>Fixed bug in <code>python_quoted_string</code> regex.</p>
</li>
<li>
<p>Added <code>examples/bf.py</code> Brainf*ck parser/executor example.
Illustrates using
a pyparsing grammar to parse language syntax, and attach executable AST
nodes to
the parsed results.</p>
</li>
</ul>
<h2>Version 3.1.0b1 - April, 2023</h2>
<ul>
<li>
<p>Added support for Python 3.12.</p>
</li>
<li>
<p>API CHANGE: A slight change has been implemented when unquoting a
quoted string
parsed using the <code>QuotedString</code> class. Formerly, when
unquoting and processing
whitespace markers such as \t and \n, these substitutions would occur
first, and</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/c09eb6e4bb283b375e53cfe851bb6a63ed3957bb"><code>c09eb6e</code></a>
Minor update to HowToUsePyparsing.rst</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/395431ab3db9cfe59ddcb22b431caea74e623a1e"><code>395431a</code></a>
Prep for release</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/54b39a52dce9a0e438b11c76bc6e1dddaf490333"><code>54b39a5</code></a>
Fix regression in SkipTo when ignoring an ignoreExpr, and failed to also
igno...</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/411c8ab6f697cb7b96f7fd1af37fefe9e3ce422b"><code>411c8ab</code></a>
Handle case where Word(min &gt; 1) with differing init and body
chars</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/1936b36823ae162698dff5184061d71e5d0bd39b"><code>1936b36</code></a>
Handle case where Word(min &gt; 1) (fixes <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/502">#502</a>)</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/421e0fcdbc76fcfb43de9c97c89872bc485d8d40"><code>421e0fc</code></a>
Update timestamp and CHANGES file to reflect recent PRs; added another
test t...</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/1355e76c16f74b387c41d26bbf4ff4338fcde0c4"><code>1355e76</code></a>
Merge branch 'pyparsing_3.1.x'</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/173bc165780cc455ba2f4818c94f0b58cb8b6e5e"><code>173bc16</code></a>
Merge pull request <a
href="https://redirect.github.com/pyparsing/pyparsing/issues/493">#493</a></li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/5b939ccc12e6213edbcecca7546472561788f3e9"><code>5b939cc</code></a>
Use reset_pyparsing_context for each example in test_examples.py</li>
<li><a
href="https://github.com/pyparsing/pyparsing/commit/eb9db9eb65f973f59d2c42ef20c6bb6cd974059a"><code>eb9db9e</code></a>
Add common, unicode, and testing to <strong>all</strong></li>
<li>Additional commits viewable in <a
href="https://github.com/pyparsing/pyparsing/compare/pyparsing_3.0.9...3.1.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyparsing&package-manager=pip&previous-version=3.0.9&new-version=3.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>