RM: Fix persistent object handling issues after RM restarted
RM: Fix persistent object handling issues after RM restarted

If some persistent objects were created before RM was launched or
during the last launch period, RM can't reload those handles into
the handle entries due to the missing of hierachy information.

This will make tpm2 create/load cmd fail when the parent handle
is a old persistent handle since it can't be found in the handle
map. This will also make tpm2 evict control return 0xa000a, since
after tpm returns response, it the handle will not be able to be
found in the handle map.

For evict control case, simply omit the entry missing failure for
persistent object is ok.

For create/load case, if parent is a old persistent object, skip
the entry matching and set the current hierarchy to TPM_RH_NULL as
a workaround.

The worst case will be that several handle map entries w/ NULL
hierarchy will not be able to be cleared by hierarchy change cmds,
but they will be released when the owner connection finished.

Not perfect, but it is already the most optmized solution.

Signed-off-by: Gang Wei<6d5a647491850fa33af0ccb95e6ed20e2ffd2d4e@intel.com>

01org/TPM2.0-TSS,01org/tpm2-tss,01org/TPM2.0-TSS,tpm2-software/tpm2-tss,01org/TPM2.0-TSS,tpm2-software/tpm2-tss,01org/tpm2-tss,01org/TPM2.0-TSS,tpm2-software/tpm2-tss,01org/tpm2-tss