Allow incremental renaming based on file metadata such as date order, not just alphabetical order

### Description of the new feature / enhancement

I’m posting here to suggest an important feature for PowerRename.

At the moment, when using incremental numbering, the files are processed in alphabetical order rather than by file metadata such as Date Modified or Date Created. That makes it a bit limiting for photo sets, scans, exports, or any batch where the chronological order actually matters more than the original filename.

I reckon It'd be very useful to have an option to apply incremental renaming based on a selected sort order, for example:
- Date modified
- Date created
- Date taken / media metadata where available
- Current Explorer sort order

The behaviour I propose: when using numbering or incrmental tokens, PowerRename could let the user choose the ordering source before applying the rename. Even a simple dropdown using the current file list order would already solve a lot.

This would make PowerRename much more useful for media handling and archive cleanup.

Thanks for considering it.

### Scenario when this would be used?

I have a batch of files that need to be renamed with sequential numbers, but the sequence needs to follow a real file timeline, not alphabetical order. Right now that workflow is difficult because numbering does not reflect the metadata order.

### Supporting information

_No response_

No files, tests, or implementation entry points are named. Start by locating PowerRename’s incremental-numbering and file-ordering logic; done means users can select a metadata or current-list order and numbering follows it, with coverage for the supported ordering choices.

Written by the indexing model from the issue text.