[HAL] Reject buffer view size overflows (#24992)

Rejects dense buffer views when shape multiplication or packed byte-size
calculation exceeds `iree_device_size_t`. Previously, overflowing
dimensions could wrap to a small value and produce an undersized
allocation request.

The size calculation now uses checked multiplication and addition while
preserving zero-dimension behavior and sub-byte element packing. Dense
view creation also verifies that the logical byte length fits within the
backing buffer, and reshape validates element counts before updating
metadata.

Tests cover:

- Shape products that wrap to zero or one.
- Packed-byte multiplication and addition overflow.
- Maximum-size byte and sub-byte element counts.
- Zero dimensions following otherwise overflowing dimensions.
- Dense views larger than their backing buffers.
- Overflowing reshape attempts.
- Native and forced 32-bit `iree_device_size_t` configurations.

Tested with:

- `iree/hal/buffer_view_util_test`
- `iree/hal/string_util_test`
- `iree/tooling/buffer_view_matchers_test`
- `iree/tooling/function_io_test`
- `iree/tooling/numpy_io_test`
- Repository pre-commit hooks for all changed files

The original `iree-run-module` reproducer was not rerun because the
validation build was configured as runtime-only without compiler tools.

This addresses the concrete buffer-view overflow case tracked in #3844.
The broader size-arithmetic audit remains open.

AI agents assisted with understanding the codebase, writing tests, and
reviewing the solution.

---------

Signed-off-by: goutamadwant <workwithgoutam@gmail.com>