storage: add support for object retention

Please implement the object retention feature. The following operations must be supported:

- [x] Create a bucket with object retention enabled by using the `enableObjectRetention` bucket create boolean option at bucket create time
- [x] Get the object retention enabled status of a bucket
- [x] Create an object with retention enabled (on an retention enabled bucket) by populating the `retention` object at object create time (retention object has the fields `mode` which can be Unlocked or Locked, and `retainUntilTime` which is a timestamp)
- [x] Update retention for an existing object with a patch operation, by passing the `overrideUnlockedRetention` boolean patch option
- [x] Get the retention policy of an object
- [x] Remove retention for an existing object the same way as above

----
Support for gRPC is blocked as the protos are not published.

- [ ] Implement FromProto for `BucketObjectRetention`
- [ ] Support `EnableObjectRetention` for gRPC plugin
- [ ] Implement ToProto and FromProto for `ObjectRetention`
- [ ] Support `OverrideUnlockedRetention` for gRPC plugin
- [ ] Support bucket metadata for object retention in the testbench
- [ ] Support object metadata for object retention in the testbench
- [ ] Upgrade the testbench
- [ ] Enable the object retention samples when running against the emulator

Details in go/gcs-object-retention-client-request

You can use the [java implementation](https://github.com/googleapis/java-storage/pull/2277) as a reference.

The kokoro test project should be allowlisted shortly, let me know if you need access to an allowlisted project for your own testing.

We're aiming to get this in by the November code freeze, let me know if you need any help.

Comienza con go/gcs-object-retention-client-request y la implementación en Java enlazada en el issue. Revisa los puntos de entrada FromProto y ToProto del plugin de gRPC y, después, las áreas de metadatos de testbench y ejemplos de emulador mencionadas en el checklist. Se considera completado cuando se hayan implementado las operaciones de retención restantes y el trabajo de soporte de testbench, sujeto a la dependencia unpublished-proto.

Escrito por el modelo de indexación a partir del texto del issue.