The `WhenReady` part of InitiateManualTranslation is redundant as we already check the necessary conditions in CanManuallyTranslate, i.e. c/1344256 makes c/1331688 redundant.

More people started used InitiateManualTranslationWhenReady, e.g. CustomTabPage (https://chromium-review.googlesource.com/c/chromium/src/+/1415263). They specifically need to trigger translate _when_ its ready, which is potentially an API we could expose in a better way then the bridge right now.
 

The `WhenReady` part of InitiateManualTranslation is redundant as we already check the necessary conditions in CanManuallyTranslate, i.e. c/1344256 makes c/1331688 redundant.

More people started used InitiateManualTranslationWhenReady, e.g. CustomTabPage (https://chromium-review.googlesource.com/c/chromium/src/+/1415263). They specifically need to trigger translate _when_ its ready, which is potentially an API we could expose in a better way then the bridge right now. For instance, they need to do custom state check (source != target) before translation, which we should support that better instead of having a custom translate function for each.