Patch rollout-batch-id even without rollout-id in workload

[PersistentJZH]

Ⅰ. Describe what this PR does

1. patch rollout-batch-id even without rollout-id in workload

Ⅱ. Does this pull request fix one issue?
#244

Ⅲ. Special notes for reviews

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.95%. Comparing base (056c77d) to head (84a0e60).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #248      +/-   ##
==========================================
- Coverage   45.55%   44.95%   -0.60%     
==========================================
  Files          57       61       +4     
  Lines        6395     7002     +607     
==========================================
+ Hits         2913     3148     +235     
- Misses       2989     3309     +320     
- Partials      493      545      +52     

Flag	Coverage Δ
unittests	44.95% <100.00%> (-0.60%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[furykerry]

simply use revision id may not works for rollback cases, rollback also support mutli-batch rollback.

[PersistentJZH]

simply use revision id may not works for rollback cases, rollback also support mutli-batch rollback.

can you give me a specific scenario so I can reproduce it? maybe can use the SafeEncodeString func to encode the revision id.

[furykerry]

maybe we can add a prefix e.g. "rollback-" to the canary revision id, so we can distinguish the pod that is not updated in previous rollout with the pod that is rollbacked. we can tell whether the rollout is a rollback using the workload.IsInRollback

[furykerry]

/lgtm
/approve