Vectorize some cases of join and advanced subtensor

[ricardoV94]

Description

Related Issue

• Closes #
• Related to #

Checklist

• Checked that the pre-commit linting/style checks pass
• Included tests that prove the fix is effective or that the new feature works
• Added necessary documentation (docstrings and/or example notebooks)
• If you are a pro: each commit corresponds to a relevant logical change

Type of change

• New feature / enhancement
• Bug fix
• Documentation
• Maintenance
• Other (please specify):

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.82%. Comparing base (b8e26cd) to head (b6ac1d9).
Report is 5 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@ ## main #744 +/- ## ========================================== + Coverage 80.81% 80.82% +0.01%  ========================================== Files 162 162 Lines 46808 46851 +43 Branches 11452 11464 +12 ========================================== + Hits 37826 37867 +41  - Misses 6734 6735 +1  - Partials 2248 2249 +1 

Files	Coverage Δ
pytensor/tensor/basic.py	88.36% <100.00%> (+0.11%)	⬆️
pytensor/tensor/subtensor.py	89.87% <100.00%> (+0.19%)	⬆️

... and 2 files with indirect coverage changes

[lucianopaz]

@ricardoV94, the vectorize on join seems fine to me but I had a couple of questions about the AdvancedSubtensor part. Once you answer those, I think that you should be good to merge.

[ricardoV94]

I put this as a staticmethod of the Op because I know we'll need to check for this case in many of the lifting rewrites, and it's nice to access it once we have a handle for the Op