Lifecycle transition is not in sync with the Cloud Backend

[kumarashit]

Issue/Feature Description: Lifecycle transition works well but the transitioned objects and corresponding bucket name doesn't reflect properly.

Why this issue to fixed / feature is needed(give scenarios or use cases): To avoid confusion for the end user

How to reproduce, in case of a bug:

1. Create Source bucket with AWS Cloud backend (ex. awsbucket)
2. Create Lifecycle transition rule for the same bucket. Transition to Azure and say for example, Tier1 from AWS to Tier 999 in Azure
3. Once the transition takes place, all the objects from AWS (source bucket) will move to the Azure backend. New Container in Azure will be created with the same name (awsbucket) Now as the Cloud Backend AWS does not have any object, after transition, the bucket in the Cloud backend will also be deleted.

Here is the issue now: SODA DB is not updated. Still the transitioned objects will be linked to old buckets. The bucket->location is older but the object.location changed in DB

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

[kumarashit]

@PravinRanjan10 please take a look. This will require some major design changes which can be analysed and put forward