Add python39/310 support back

[trim21]

we drop py<3.11 support in #4625 (reply in thread) because we don't have enough pypi space for wheel, and because of the stable API we used, we have to choose cp311.

Now we have more pypi spaces, I proposal we add these versions back without abi3 flags.

For python>=3.11, only abi3 wheel are provided.

for this proposal, what we need:

1. move pyo3 abi3 feature to top-level feature in py binding cargo.
2. change build steps to cp3.11 with abi3 feature and cp3.9/3.10 without abi3 feature.
3. change tests to add cp39/310 back and test with abi3 when py>=3.11 （if we have）

[Xuanwo]

Here are some data from the bigquery-public-data.pypi.file_downloads:

SELECT
  REGEXP_EXTRACT(details.python, r'^([0-9]+\.[0-9]+)') as python_version,
  COUNT(*) as download_count
FROM `bigquery-public-data.pypi.file_downloads`
WHERE
  file.project = 'opendal'
  AND timestamp >= TIMESTAMP(DATE_SUB(CURRENT_DATE(), INTERVAL 6 MONTH))
  AND details.python IS NOT NULL
GROUP BY python_version
ORDER BY download_count DESC;

[Xuanwo]

Please note that OpenDAL hasn't released support for version 3.10 for a long time. The actual number of 3.10 users might be even higher than shown here.

[trim21]

cp39 is arguable, but we should really consider add cp310 back

[trim21]

another options is to relex Python requirements and remove abi3 features from pyo3 so at least cp39/cp310 uses （with cargo installed） can install from sdist

[Xuanwo]

cc @Zheaoli & @PsiACE what do you think?

[PsiACE]

I think 3.10 is a good choice to get users started with the newer opendal. P.S. Our team is currently using 3.10 and has no plans to upgrade at this time, and we are not direct users of python binding.

[Xuanwo]

Thank you @trim21, this proposal has been implemented in #5347

[trim21]

still have the question about cp39