UserSessionManager trigger tpm initialization whenever TPM is enabled.

we are obsoleting `TpmIsBeingOwned()`, which is not really necessary
anyway; even if `TpmIsBeingOwned()` returns `true`, triggering the TPM
initilaization again is just no-ops at ChromeOS side.

BUG=b:172775884
TEST=TBD if untitests needed.

Change-Id: If4240a0c8a9a7485d77856e1e5c346c89407c09a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532155
Commit-Queue: Leo Lai <cylai@google.com>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#826306}

chrome/browser/chromeos/login/session/user_session_manager.cc

@@ -1544,7 +1544,7 @@ void UserSessionManager::CompleteProfileCreateAfterAuthTransfer(
 void UserSessionManager::PrepareTpmDeviceAndFinalizeProfile(Profile* profile) {
   BootTimesRecorder::Get()->AddLoginTimeMarker("TPMOwn-Start", false);
 
-  if (!tpm_util::TpmIsEnabled() || tpm_util::TpmIsBeingOwned()) {
+  if (!tpm_util::TpmIsEnabled()) {
     FinalizePrepareProfile(profile);
     return;
   }