[tests-only] Tag recursive copy scenario with issue number

[phil-davis]

Description

The new test scenario "Copying a folder into a sub-folder of itself" has similar recursive problem to the scenario "Moving a folder into a sub-folder of itself". There was a problem in reva-oCIS with this sending the server into an infinite recursion.

The problem has been fixed in reva edge branch, and in oCIS. But the inifinite recursion still happens in reva master branch. reva master branch CI has a filter for ~@issue-ocis-3023 - to avoid running the scenario(s) that have this problem.

This PR tags the new scenario so that it will not be run in reva master.

The problem was noticed when bumping the core commit id in cs3org/reva#3076 (comment)

2nd commit: bump sabre dependencies (just because patch bumps are available - not related to the skipping)

Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Lock file operations: 0 installs, 3 updates, 0 removals
  - Upgrading roave/security-advisories (dev-master 54cbc13 => dev-master 0144c12)
  - Upgrading sabre/http (5.1.5 => 5.1.6)
  - Upgrading sabre/vobject (4.4.2 => 4.4.3)
Writing lock file

How Has This Been Tested?

CI

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[SagarGi]

lgtm 👍

[phil-davis]

@SagarGi can you give a "green tick" approval please, so that I can merge this PR.