rgw: fix bucket re-creation on secondary region

We had a problem with bucket recreation, where we identified
that bucket has already existed, but missed the fact that it's
the same bucket, so removal of the bucket index was wrong.

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: forward x_amz_meta headers when forwarding a request

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: adjust error for bucket removal on secondary region

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: forward delete bucket request to master after removal

We can only forward the bucket removal to the master if it was
successfully removed locally.

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: remove s->objv_tracker

was never initialized correctly anyway. It was only supposed to
be used for buckets, but it was never initialized in that case.
Using s->bucket_info.objv_tracker instead.

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: bucket entry point object ver fixes

Multiple fixes:
 - sync master, secondary entry point ver on creation
 - use correct entry point version when removing entry point
 - check correct version on bucket removal

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: resurrect a line that was accidentally dropped.

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: fix time parsing in replica log

Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>