AlgoScan

skip-checks: true

Bumps [requests](https://github.com/psf/requests) from 2.32.5 to 2.33.0.
- [Release notes](https://github.com/psf/requests/releases)
- [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md)
- [Commits](https://github.com/psf/requests/compare/v2.32.5...v2.33.0)

---
updated-dependencies:
- dependency-name: requests
  dependency-version: 2.33.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [pygments](https://github.com/pygments/pygments) from 2.19.2 to 2.20.0.
- [Release notes](https://github.com/pygments/pygments/releases)
- [Changelog](https://github.com/pygments/pygments/blob/master/CHANGES)
- [Commits](https://github.com/pygments/pygments/compare/2.19.2...2.20.0)

---
updated-dependencies:
- dependency-name: pygments
  dependency-version: 2.20.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

fix: include v5 migration guide in starlight docs

The replace folding paths used Python's bytearray slice assignment,
which silently grows the array when the replacement extends past the
source. The AVM panics with "replacement end N beyond original
length: M" in this case.

Now returns None (skip fold) when start + len(replacement) >
len(source), preserving the runtime panic.

The intrinsic simplifier folds replace2/replace3 even when the
replacement extends past the source. Python's bytearray slice
assignment silently grows the array, masking the AVM's runtime panic.

The shl/shr folding paths had no bounds check on the shift amount.
For shift >= 64, the AVM panics with "shl/shr arg too big", but the
optimizer computed (a << b) % 2^64 or a >> b, silently producing 0.

Now the match cases have guard clauses `if b_const < 64`, skipping
the fold when the shift would be out of bounds.