[BUG]: verify_preprocessing() stores resolved path instead of original in VerificationReport

### Bug Description

## Description
`verify_preprocessing()` calls `Path.resolve()` on the user-supplied
`input_dump` before storing it in `VerificationReport.input_dump`.
On Windows, `resolve()` can alter path casing via junction point
expansion, causing `report.input_dump != str(original_path)`.

## Failing Test
`tests/test_verify.py::TestHappyPath::test_report_stores_input_dump_path`

## Expected Behaviour
`report.input_dump` should equal the original path string passed by the caller.

## Actual Behaviour
On Windows, the stored path may differ in casing from the original.

### Steps to Reproduce

1. Clone the repository on Windows
2. Run `pytest tests/test_verify.py::TestHappyPath::test_report_stores_input_dump_path -v`
3. Observe the test fails

### Logs and Screenshots

### Environment Details

-OS : Windows 11

### Impact

Medium - Feature works but has issues

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates