Fix: handle appKey conflicts

[dorjesinpo]

1. Refactor thread-unsafe mqbi::Storage::loadVirtualStorageDetails call on the cluster thread.
2. appId is the only key for mqbi::Storage::AppInfos
3. Workaround for the appKeys conflict (CSL vs. Qlist)

[kaikulimu]

On the subject of thread-unsafe mqbi::Storage::loadVirtualStorageDetails calls, we need to fix one call inside mqbblp::Cluster::onRecoveryStatusDispatched.

[kaikulimu]

Some comments, and to to fix one call inside mqbblp::Cluster::onRecoveryStatusDispatched.

[dorjesinpo]

On the subject of thread-unsafe mqbi::Storage::loadVirtualStorageDetails calls, we need to fix one call inside mqbblp::Cluster::onRecoveryStatusDispatched.

Indeed. I thought, we can leave it as-is for now. Supposedly, d_recoveryStatusCb cannot be concurrent with any add/removeVirtualStorage (please, double-check).
Otherwise, we could do something like Dispatcher::execute followed by Dispatcher::synchronize.

[bmq-oss-ci]

Build 409 of commit 72e9a1c has completed with FAILURE

[kaikulimu]

lgtm