nanobind type caster between C++ Array/Vector and python cocotb.types.Array

[ZiaCheemaGit]

Fixes #267

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.97%. Comparing base (6a35641) to head (96f361a).
⚠️ Report is 5 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #288      +/-   ##
==========================================
- Coverage   92.76%   91.97%   -0.79%     
==========================================
  Files          23       23              
  Lines        1285     1309      +24     
  Branches      312      316       +4     
==========================================
+ Hits         1192     1204      +12     
- Misses         34       43       +9     
- Partials       59       62       +3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ZiaCheemaGit]

Best reviewed commit by commit

[ktbarrett]

This is also looking very good for a first pass.

[ktbarrett]

If we have successfully patched cocotb.types.Range with coconext's versions we should be able to just nb:cast<Range>(src.attr("range")) to get the range object.

Though I understand being defensive about it.

[ktbarrett]

Also do the same changes for the Vector type.

The left and right are no longer limited to int, but to int64_t. It's best to just call out Array::index_t instead, just incase we change it again, like I did from int to int64_t.

I'm wondering if you can cut down on verbosity by using using namespace coconext::types in the caster method bodies?

[ktbarrett]

Merge when you are ready.