Carry forward |allow_tts| for deep link queries.

If the user taps a card in an Assistant response, we want to carry
forward the allowance/forbiddance of TTS from the preceding query.

This is analogous to what we are currently doing for suggestion chip
press handling.

The difference here is that there are potentially other sources for
deep links than just cards (e.g. notifications). If this behavior
doesn't work for those use cases we can expose an explicit |allow_tts|
parameter to the deep link for deep link creators, but I think this
should be sufficient behavior for the time being.

Bug: b:124399429
Change-Id: I00251749281591623f28e7a90b8d1e19f0fa3eed
Reviewed-on: https://chromium-review.googlesource.com/c/1476064
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#632926}
1 file changed