[full-ci] Bump punic/punic from 3.7.0 to 3.8.0

[dependabot]

Bumps punic/punic from 3.7.0 to 3.8.0.

Release notes

Sourced from punic/punic's releases.

v3.8.0

• Upgrade version of CLDR data from 40 to 42 (#417, punic/data#19, @​mlocati)

Changelog

Sourced from punic/punic's changelog.

3.8.0 (2022-10-19)

• Upgrade version of CLDR data from 40 to 42 (#417, punic/data#19, @​mlocati)

Commits

• f24eb48 [skip ci] Update APIs
• ce8557e Prepare version 3.8.0
• d18bac8 Merge pull request #417 from mlocati/cldr-42
• 850150a Upgrade CLDR data to v42
• da1deab Execute tests with PHP 8.2 too, test more Windows cases
• f540aa6 [skip ci] Update APIs
• c8525ce Prepare for next version
• 847bd53 [skip ci] Update APIs
• See full diff 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 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)

[phil-davis]

@dependabot rebase

[phil-davis]

https://drone.owncloud.com/owncloud/core/37113/9/7

There were 21 failures:

1) Test\DateTimeFormatterTest::testFormatDateTime with data set #0 (1350129205, null, 'October 13, 2012 at 11:53:25 AM UTC')
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'October 13, 2012 at 11:53:25 AM UTC'
+'October 13, 2012, 11:53:25 AM UTC'

/drone/src/tests/lib/DateTimeFormatterTest.php:166
phpvfscomposer:///drone/src/lib/composer/phpunit/phpunit/phpunit:97
...

something has changed with the date format locales/defaults.

[phil-davis]

https://drone.owncloud.com/owncloud/core/37268/9/7

There were 16 failures:

1) Test\DateTimeFormatterTest::testFormatDateTime with data set #0 (1350129205, null, 'October 13, 2012, 11:53:25 AM UTC')
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'October 13, 2012, 11:53:25 AM UTC'
+'October 13, 2012, 11:53:25 AM UTC'
...

The expected and actual strings look the same, but there are some special characters in the actual strings.
Needs investigation.

[phil-davis]

A bit of investigation:

1) Test\DateTimeFormatterTest::testFormatDateTime with data set #0 (1350129205, null, 'October 13, 2012, 11:53:25 AM UTC')
expected: 4f63746f6265722031332c20323031322c2031313a35333a323520414d20555443
  actual: 4f63746f6265722031332c20323031322c2031313a35333a3235e280af414d20555443
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'October 13, 2012, 11:53:25 AM UTC'
+'October 13, 2012, 11:53:25 AM UTC'

The actual string returned has "e280af" between the time "11:53:25" and the letters "AM".

https://bugs.php.net/bug.php?id=77914 (the change in this PR is not related to that non-bug, but the bug comments are useful)
"e280af" represents a NARROW NO-BREAK SPACE

It seems that the latest databases that punic is now using are putting this Unicode character within the time string. That seems reasonable - we do not want date-time strings to be wrapped at that point. For example:

We worked most of the morning and then looked at our phones and it was October 13, 2012, 11:53:25
AM UTC. We had to run to catch the train.

With the NARROW NO-BREAK SPACE we would get:

We worked most of the morning and then looked at our phones and it was October 13, 2012,
11:53:25 AM UTC. We had to run to catch the train.

And that is a smarter wrap of the date-time string.

I will adjust the test expectations.

[phil-davis]

I also pushed a commit to update symfony dependencies that are waiting:

Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 9 updates, 0 removals
  - Upgrading roave/security-advisories (dev-master 1d3484a => dev-master 5317244)
  - Upgrading symfony/console (v4.4.47 => v4.4.48)
  - Upgrading symfony/polyfill-iconv (v1.26.0 => v1.27.0)
  - Upgrading symfony/polyfill-intl-idn (v1.26.0 => v1.27.0)
  - Upgrading symfony/polyfill-intl-normalizer (v1.26.0 => v1.27.0)
  - Upgrading symfony/polyfill-mbstring (v1.26.0 => v1.27.0)
  - Upgrading symfony/polyfill-php72 (v1.26.0 => v1.27.0)
  - Upgrading symfony/polyfill-php73 (v1.26.0 => v1.27.0)
  - Upgrading symfony/polyfill-php80 (v1.26.0 => v1.27.0)
Writing lock file

[phil-davis]

https://drone.owncloud.com/owncloud/core/37279/23/7 fails due to known issue #40457 - I will manually change the drone result to a pass, and then merge this PR.