chore(passport): Optimize pre-authz to retain personaData within DO

[betimshahini]

The current implementation of pre-authorization relies on the chain of storing authorization data in Authorization DO until the code is exchanged for the token, at which point it persists the same data in the Access DO. This was done to leverage the interfaces that are already there being used for the non-pre-authz scenario.

The pre-authz screnario should optimize the data access so that the data already contained in the previously authorization contained within the Access DO, does not need to be travel to the Authorization node to then come back to the Access node for the pre-authz case.