GitLab

The basic strategy is as follows:
- Assistant UI creates suggestion chip w/ icon placeholder.
- Assistant UI requests icon download from AssistantController.
- AssistantController requests download from AssistantImageDownloader.
- AssistantImageDownloader downloads image using BitmapFetcher.
- On success, AssistantImageDownloader runs callback to Assistant UI.
- Assistant UI updates icon for suggestion chip view.

This is a similar flow to what is currently done for rendering
Assistant cards. The BitmapFetcher logic is modeled on what is
currently done by AccountAvatarFetcher.

See bug for demo.

Bug: b:79599200
Change-Id: I9ee09a2458ce955a5e4926fcef43864a05e4454e
Reviewed-on: https://chromium-review.googlesource.com/1066179Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#561724}