Rethink import/export with secrets

(Migrated from https://github.com/syndesisio/syndesis/issues/3423)

Author: Zoran Regvart
Assignees: unassigned

This is a...

[!-- Check ONLY one of the following options with "x" --]
[pre][code]
[x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report [!-- Please search GitHub for a similar issue or PR before submitting --]
[ ] Documentation issue or request
[/code][/pre]
[!-- If possible, please choose the appropriate labels for your issue. You find a description of all
labels used at https://doc.syndesis.io/#dev-labels --]

The problem

[!--
Briefly describe the issue you are experiencing (or the feature you want to see implemented on Syndesis).
+ For BUGS, tell us what you were trying to do and what happened instead.
+ For NEW FEATURES, describe the User Persona demanding it and its use case.
--]
We're recurringly stumbling with managing imports/exports of integrations containing secrets (e.g. passwords for database connection). Perhaps we should rethink our approach. Perhaps it would be better to prompt the user for export password and re-encrypt the secret content with that export password that'll also be needed when importing the integration.

Expected behaviour

[!-- Describe what the desired behavior would be, enlistin gthe acceptance criteria. --]
No more reports like #3404 #2603 #2602 #2585

Screenshot

[!--
For features/bugs tackling with UI functionality, drag and drop a screenshot depicting the desired presentation layer or supporting the UX narrative for the new functionality.
--]
!giphy

Tasks involved / Steps to Reproduce

[!--
Enlist all the acceptance criteria for new features or the steps required to reproduce the bug/regression reported.
--]
1. On export prompt for a password, decrypt secrets with instance key and re-encrypt with given password
2. On import prompt for a password, decrypt secrets with given password and re-encrypt with instance key

4.