Allow to select an existing security to replace a newly imported one

[buchen]

When reviewing the newly created items, the user can choose to replace a new security with an existing security. All transactions are then imported and added to the existing security.

• Extended ExtractedEntry with security dependency (= if an extracted entry depends on another extracted security) and security override (= if the user chose to replace the imported security with an existing security)
• Refactored the import logic into ImportController to allow sharing between PDF and CSV imports

Bildschirmaufnahme.2023-08-09.um.16.41.28.mp4

[Nirus2000]

Maybe that way better for understanding the code?

    // Import if the status is OK or the user explicitly overrides warnings
    if (maxCode == Status.Code.OK) {
        return true;
    }

    // Import if warnings are explicitly allowed or if it's an investment plan item
    return maxCode == Status.Code.WARNING && (isImported != null && isImported.booleanValue()
            || item.isInvestmentPlanItem());

[buchen]

It was only a formatting change - maybe I should remove even the formatting from the commit.

I am also not sure if the statements are identical due to the missing parenthesis.

[Nirus2000]

This is very nice... i ❤️‍🔥 it...

[siprbaum]

On a technical level, I understand what the feature can do, but I am struggling a little for which use cases I would use it.

Would this be helpful e.g. when a security was merged/replaced by another?
E.g. in the past, the Lyxor MSCI World (WKN: ETF110) was merged/replaced by Amundi MSCI World (WKN: ETF018).
The bank automatically exchanged the existing ETF110 in the depot with Amundi ETF018 shares.

Any pointer to existing uses cases/documentation when to use this feature would be appreciated.