Investigate if a transport parameter is needed for `REST` LRO client classes

We currently have separate client classes for each combination of `[async, sync] x [gRPC, REST]` transports. We also maintain separate transport classes for REST.

Given the above case, it's worth figuring out if a transport parameter adds any value in the `REST` client classes.
