Bump phpseclib/phpseclib from 2.0.29 to 2.0.31 in /civicrm

Bumps [phpseclib/phpseclib](https://github.com/phpseclib/phpseclib) from 2.0.29 to 2.0.31.
- [Release notes](https://github.com/phpseclib/phpseclib/releases)
- [Changelog](https://github.com/phpseclib/phpseclib/blob/master/CHANGELOG.md)
- [Commits](https://github.com/phpseclib/phpseclib/compare/2.0.29...2.0.31

)

Signed-off-by: dependabot[bot] <support@github.com>

PR 18980  Christian Wach

https://github.com/civicrm/civicrm-core/pull/18967 from Seamus Lee

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

updated for 5.29.0

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>

Tim Otten authored 4 years ago and Kevin Cristiano committed 4 years ago

This is a refinement of the idea in https://github.com/civicrm/civicrm-wordpress/pull/135

 to address other CLI use-cases.

Before
-------

If I have a `wpmaster` site on on `bknix-max` (php73), and if I run `cv upgrade:db -vv`, then there are several warnings like this:

After
-----

It doesn't try to start session in CLI (where sessions don't make sense).

Signed-off-by: Kevin Cristiano <kcristiano@kcristiano.com>