bisect-kit: Fix ./diagnose_cros*.py view --timestamp

It is somehow tricky to reproduce a view.json at some past timestamp.

In previous implementation, strategy.rev_info is synced to the
past timestamp. However other internal state of strategy is not synced
to the specific timestamp. So the strategy object ends up to be in an
inconsistent state.

In the new implementation, we create a new strategy object and add each
historical samples one by one to reply the bisect process. In the way
the strategy object would be in a consistent state.

BUG=b:335132250
TEST=./diagnose_cros_tast.py  view --timestamp <timestamp>

Change-Id: I8a43063534dbc468d9d0d1f4d0fe7326016d817f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bisect-kit/+/5653973
Tested-by: Cheng-Yu Lee <cylee@google.com>
Reviewed-by: MD Nayeem Jahan Rafi <njrafi@chromium.org>
Commit-Queue: Cheng-Yu Lee <cylee@google.com>
4 files changed