return unsupported for read/stat/delete with version when versioning is not enabled

[meteorgan]

Which issue does this PR close?

None

Rationale for this change

As discussed in: #5132 (comment)
We should return Unsupported error for every operation with version when versioning is not enabled

What changes are included in this PR?

Are there any user-facing changes?

[Xuanwo]

Hi, this PR suggests that we consider introducing a layer to handle unsupported behaviors. Not all users and use cases are concerned about whether services support versioning; they might simply want to write code consistently and return it as is if not supported.

---

We have similar code here:

opendal/core/src/layers/complete.rs

Lines 132 to 140 in d479ac3

	fn new_unsupported_error(&self, op: impl Into<&'static str>) -> Error {
	let scheme = self.meta.scheme();
	let op = op.into();
	Error::new(
	ErrorKind::Unsupported,
	format!("service {scheme} doesn't support operation {op}"),
	)
	.with_operation(op)
	}

I think we can create a new layer called CapabilityCheckLayer. By default, opendal will not perform any capability checks. Users can enable CapabilityCheckLayer to ensure the features they use are supported and behave as expected.

CapabilityCheckLayer may have different modes:

• Default: just bypass all checks, like the opendal default behavior.
• Correctness: only check capability that affected correctness, for example, write with if none match, read with version.
• All: check all capabilities.