Fixes behaviour of includeAll by keeping the trailing slash on the path

[filipelautert]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

PR #3355 aimed to fix issues related to "./" and "../" , but by using Paths.get it is also removing trailing slashs. The changed method has logic to append the trailing slash, but it is located above the new code - so it baceme useless. This PR moves the code that fixes the path to be executed after Paths.get.

Things to be aware of

• Fixes includeAll on S3 extension.
• Tests restored as they were before Fix include/includeAll to correct track relativeToChangelog=true paths using ./ or ../ #3355

Things to worry about

• None

Additional Context

• Issue raised by S3 extension tests.

[github-actions]

Unit Test Results

  4 776 files  ±  0    4 776 suites  ±0   32m 47s ⏱️ + 1m 28s
  4 735 tests +18    4 502 ✔️ +21     233 💤  - 3  0 ❌ ±0 
55 836 runs  +12  50 508 ✔️ +17  5 328 💤  - 5  0 ❌ ±0 

Results for commit 13b8247. ± Comparison against base commit 729d8b0.

[XDelphiGrl]

PR addresses a regression introduced while fixing the path shown in some output messages and the value stored in DATABASECHANGELOG tracking table when include or includeAll changesets specify relativeToChangelog=true. The original fix was too broad, and stripped trailing as well as leading slashes; only leading should be removed. This fix restores the correct behavior of keeping trailing slashes.

• Automated functional and test harness executions passing.
• S3 extension test that exposed the bug is fixed by this PR.
• New unit test added.
• No additional testing required.

APPROVED