…reen>

when the wizard_controller is initialized it starts off with a different
profile from the user profile. The `IsOobeDrivePinningEnabled()` returns
false at this point and doesn't include the DrivePinningScreen to
screen_manager. Later on when the user has passed the login screen and
is at the consent screen, the `IsOobeDrivePinningEnabled()` returns true
and tries to get the DrivePinningScreen to kick off CalculateRequiredSpace
but it was never added due to the first false call.Use Same condition
IsOobeDrivePinningEnabled() when initialize handler.
do not include kFeatureManagementDriveFsBulkPinning in the check
IsOobeDrivePinningEnabled as there is an exception for googler users.

(cherry picked from commit 2090a104a0c04a013ed3a2ae2427cb97fd88b254)

Bug: 1480014, b:299078820, b:300615576
Change-Id: I575a764d3b0357423491c3b378134e4d59ab4abc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4874797
Reviewed-by: Ben Reich <benreich@chromium.org>
Reviewed-by: François Degros <fdegros@chromium.org>
Reviewed-by: Danila Kuzmin <dkuzmin@google.com>
Commit-Queue: Brahim Chikhaoui <bchikhaoui@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1198234}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4876058
Commit-Queue: Ben Reich <benreich@chromium.org>
Cr-Commit-Position: refs/branch-heads/5993@{#596}
Cr-Branched-From: 511350718e646be62331ae9d7213d10ec320d514-refs/heads/main@{#1192594}