fix(task) #16 ZipTask: only remove the leading files_base_path, read relative paths from the current directory

[njoubert-cleverage]

Description

Fixes #16. Based on #19 (merge it first, this PR will then target main).

ZipTask built the archive entry names with str_replace($files_base_path, '', $file) and always prefixed the read path with files_base_path.'/':

• every occurrence of files_base_path was removed, not only the leading one: a path containing it again was looked for at a wrong path (File does not exists);
• with the default empty files_base_path, relative paths were resolved from the filesystem root.

Changes:

• ZipTask::execute(): remove files_base_path only when the path starts with it followed by a directory separator (a trailing separator in files_base_path is ignored); other paths stay relative to files_base_path, as before. With an empty files_base_path, read the file at the given path (absolute or relative to the current directory); the entry name is unchanged (the path without its leading /)
• ZipTaskTest: a path containing files_base_path twice, a relative path without files_base_path (both fail without the fix)
• zip_task.md: update the files option and the notes

Checked with demo.archive.zip_files_base_path (entry demo_zip_files_base_path/backup/var/data/archived_file.txt) and demo.archive.zip_relative_path (entry var/data/sample.txt) in process-bundle-demo: both failed with File does not exists before.

Requirements

• Documentation updates
  • Reference
  • Changelog
• Unit tests

Breaking changes

None: the affected configurations failed (File does not exists) or added the wrong file. Absolute paths starting with files_base_path (once) and paths relative to files_base_path behave as before.

🤖 Generated with Claude Code