Ignore and log non integer versions

[come-nc]

This avoids being stuck when there is one buggy file version with a
non-numeric version. It allows the expiration process to not crash and
continue with the other ones.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[blizzz]

This avoids being stuck when there is one buggy file version with a
non-numeric version.

What's the root cause?

[come-nc]

This avoids being stuck when there is one buggy file version with a
non-numeric version.

What's the root cause?

No idea, might be moving file to/from groupfolders, or a buggy application.
This is to help debugging this case and not have the whole version expiry system crash down because of one badly named file.

[come-nc]

/backport to stable26

[solracsf]

/backport to stable27

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[come-nc]

/backport to stable27

It’s already in 27