feat(tests): Introducing BDD tests for all bindings

[Xuanwo]

This pull request aims to introduce Behavior-Driven Development (BDD) tests for all of our bindings. It serves as a proof-of-concept and uses the Python binding as an example.

Moving forward, we will maintain the same feature file for all bindings. Only when a binding passes all feature tests will it be marked as ready.

Here is an example using Python:

:) behave tests
Feature: OpenDAL Binding # tests/binding.feature:18

  Scenario: OpenDAL Blocking Operations                             # tests/binding.feature:20
    Given A new OpenDAL Blocking Operator                           # tests/steps/binding.py:23 0.000s
    When Blocking write path "test" with content "Hello, World!"    # tests/steps/binding.py:27 0.000s
    Then The blocking file "test" should exist                      # tests/steps/binding.py:31 0.000s
    Then The blocking file "test" entry mode must be file           # tests/steps/binding.py:35 0.000s
    Then The blocking file "test" content length must be "13"       # tests/steps/binding.py:39 0.000s
    Then The blocking file "test" must have content "Hello, World!" # tests/steps/binding.py:43 0.000s

  Scenario: OpenDAL Async Operations                             # tests/binding.feature:28
    Given A new OpenDAL Async Operator                           # tests/steps/binding.py:48 0.000s
    When Async write path "test" with content "Hello, World!"    # tests/steps/binding.py:53 0.001s
    Then The async file "test" should exist                      # tests/steps/binding.py:58 0.000s
    Then The async file "test" entry mode must be file           # tests/steps/binding.py:63 0.000s
    Then The async file "test" content length must be "13"       # tests/steps/binding.py:69 0.000s
    Then The async file "test" must have content "Hello, World!" # tests/steps/binding.py:75 0.000s

1 feature passed, 0 failed, 0 skipped
2 scenarios passed, 0 failed, 0 skipped
12 steps passed, 0 failed, 0 skipped, 0 undefined
Took 0m0.002s

• close Create a mock serivces to allow testing our bindings #1521
• close Implement mock services to test our bindings #1550

[Xuanwo]

I would also like to invite the maintainers of bindings, @suyanhanx and @messense for review.

[Xuanwo]

For nodejs: https://github.com/cucumber/cucumber-js
For C: https://github.com/cucumber/cucumber-cpp

Going forward, BDD test frameworks for Go, Lua, and Java will be used independently.

[PsiACE]

It seems that BDD would be a good choice when not involving the details of implementation. I have a positive attitude towards this PR overall. I need some time to check it, and also look forward to suggestions from other bindings' maintainers.

[suyanhanx]

This form of testing is quite good for us. It helps to ensure consistency between various bindings, and reasonably splitting test files provides some guidance for synchronizing the functionality of new bindings.