Lazily register TranslateKit component

This CL delays TranslateKit component registration until the Translation
API is first used.

Specifically:
- Previously, the TranslateKit component was registered on startup if
  the EnableTranslateKitComponent feature was enabled. This can cause
  unnecessary overhead for users who do not use Translation API.
- Now, the component is only registered after the Translation API is
  called.
- CreateTranslator() requests now wait for the TranslateKit component to
  be installed before proceeding.
- The CanTranslate() method will quickly return false if the
  TranslateKit component is not available.

Bug: 358030919
Change-Id: I05caaa939cbace31be3f9fdc34178ce0a59f2a8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5905017
Reviewed-by: Ming-Ying Chung <mych@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1366176}