[PERF]: Handle generic sequences more efficiently

In driver, runtime and nvrtc, most of the sequence arguments are of a type like Optional[tuple[cuuint64_t] | list[cuuint64_t]].

They are then converted to C arrays using code like:

for idx in range(elementStridesLen):
            elementStridesStatic[idx] = <cydriver.cuuint32_t>(<cuuint32_t?> elementStrides[idx])._pvt_ptr[0]

elementStrides[idx] here uses the generic PySequence_GetItem, which first must check whether the sequence is a list or tuple before getting the item. This check is performed repeatedly for each item, even though the type of the sequence remains constant. The branch predictor may or may not be able to smooth this out.

Ideally, we would use the PySequence_Fast family of functions. Unfortunately, Cython's wrappers of low-level Python/C API functions involving borrowing are broken -- we would probably need to revert to raw C snippets to make that work.

Alternatively, we could do something like:

if type(seq) is list:
    for idx in range(len(seq)):
        # use cpython.PyList_GetItemInt...
elif type(seq) is tuple:
    for idx in range(len(seq)):
        # use cpython.PyTuple_GetItemInt...

Start by locating the generic sequence-conversion loops in the driver, runtime, and nvrtc areas. Read the Cython wrappers around the sequence access and the documented PySequence_Fast APIs, then compare the possible access paths described in the issue. Done means the affected conversions use an efficient supported approach without changing their behavior.