The `extended-history-by-registrar` option in account history plugin does not track LTM correctly

**User Story**

Background:
* We added the `extended-history-by-registrar` option to the account history plugin via https://github.com/bitshares/bitshares-core/pull/2259 to track accounts with extended parameters.

Issue:
* If an account is registered by a registrar we track and then it upgraded to LTM, the plugin no longer tracks it with extended parameters.

**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [ ] API (the application programming interface)
- [ ] Build (the build process or something prior to compiled code)
- [ ] CLI (the command line wallet)
- [ ] Deployment (the deployment process after building such as Docker, Travis, etc.)
- [ ] DEX (the Decentralized EXchange, market engine, etc.)
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
- [ ] Performance (system or user efficiency, etc.)
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [x] UX (the User Experience)
- [x] Other (please add below)
- account history plugin

**Additional Context (optional)**
Add any other context about your request here.

## CORE TEAM TASK LIST
- [ ] Evaluate / Prioritize Feature Request
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation

Start by tracing the account history plugin's `extended-history-by-registrar` handling for accounts that upgrade to LTM. Reproduce the registrar-then-LTM transition and verify that the account remains tracked with extended parameters; add or update coverage if the repository's existing plugin tests expose this path.

Written by the indexing model from the issue text.