Support Multi‑Step / Multi‑URL Navigation for Auto‑Fill in Complex Login Flows

[elpezganzo]

Summary:

Some web applications require navigating through multiple intermediate URLs or user actions before reaching the final login form. Currently, ChromeKeePass/EdgeKeePass appears to only match and auto‑fill credentials on one page (URL field in KeePass).

Example Scenarios:

Scenario 1:

1. Navigate to: https://my.app.domain.com/restofdata
2. Page automatically redirects to: https://my.appfinal.finaDomain.com/restofdataFinal
3. Login form (username/password) is presented on the final URL. Note: Loading the first URL is required for the final page to work correctly.

Scenario 2:

1. Navigate to: https://tt.domainW.com/blahblah
2. Click a link on the page → redirects to: https://zz.exfinal.xDomain.com/x/a/etc
3. On this page, a text field must be auto‑filled with a custom value: "DomainX"
4. After submission, redirected to: https://ppDomainZ.eu/blahblah where username/password are requested.

Feature Request:

Add support for defining multiple URLs taken from KeePass String fields entries like KBH: URL_#... so that auto‑fill can be triggered after intermediate navigation steps. To use the KBH: URL_#... entries to URL filter instead of field inclusion.