Python frontend stability and inline storage specification

[tbennun]

The PR adds a new syntax to support inline storage specification with the @ operator, supporting the following statements: a = np.ones(M) @ dace.StorageType.CPU_ThreadLocal.

This PR also fixes multiple minor issues in the Python frontend:

• WarpTiling did not respect sequential map schedules
• Non-sequence inputs for numpy.fill variants (e.g., numpy.zeros(N))
• NumPy replacement syntax errors would sometimes not have source information
• Fix type inference for nested scopes in Python frontend
• Dynamic map range related issues with simple modifications to the SpMV program Fix deferred to No-View Nested SDFGs #1696
• Dynamic thread block scheduling would not pass object to nested functions Fix deferred to future PR, see Support nested SDFGs in ScheduleType.GPU_ThreadBlock_Dynamic #1189
• Dynamic thread block scheduling does not support multi-dimensional maps
• Default schedule inference should use dynamic thread blocks if they exist
• Type hints with storage type not being adhered to by the Python frontend
• Validation issue sdfg.validate goes on infinite recursion with loopy sdfg #1562

[phschaad]

Nothing to add, LGTM. Looks like one GPU test fails due to wrongful arglist construction for a nested SDFG. I have encountered a similar issue numerous times on #1676 and fixed it there, but I suspect that the newly merged #1708 also fixed the issue? I have updated with main to verify.