add clear task method and made close an alias

[zhindes]

• This contribution adheres to CONTRIBUTING.md.
• I've updated CHANGELOG.md if applicable.
• I've added tests applicable for this pull request

What does this Pull Request accomplish?

I had some customer feedback that clear task was more familiar for people coming from other DAQmx APIs, which I agree with. In practice, tasks should almost always be used with Python context managers, but in the rare cases where they aren't, this method could be useful.

Why should this Pull Request be merged?

Simple rename of an existing method with an alias to the old name to not break compatibility.

What testing has been done?

Added a unit test, and ran all the existing ones. griffe says:

>poetry run griffe check -s generated\ -a 1.5.0 --verbose nidaqmx
generated\nidaqmx\task\_task.py:364: Task.close:
Public object points to a different kind of object:
  Old: function
  New: attribute

Their documentation says:

Changing the kind of an object is not really an API breakage, depending on our definition of API, since this won't always raise immediate errors like TypeError. The object is still here and accessed: the contract is fulfilled. But developers sometimes rely on the kind of an object, so changing it will lead to incorrect behavior, potentially making it difficult to detect, understand and fix the issue. That is why it is important to warn developers about such changes.

[github-actions]

Test Results

    46 files  ± 0      46 suites  ±0   1h 17m 50s ⏱️ -45s
 3 211 tests + 2   2 558 ✅ + 2     653 💤 ±0  0 ❌ ±0 
62 022 runs  +56  49 192 ✅ +56  12 830 💤 ±0  0 ❌ ±0 

Results for commit fe3ebc5. ± Comparison against base commit e18602c.