The issue was reported on the Debian bugtracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123931

I wonder if the constraints:

Breaks: mesa-va-drivers (<< 25.2.8-3), mesa-vdpau-drivers (<< 25.2.8-3)
Replaces: mesa-va-drivers (<< 25.2.8-3), mesa-vdpau-drivers (<< 25.2.8-3)

are too strict, and should read <= instead. I will try to reproduce it.

EDIT: no, it's not a problem caused by << 25.2.8-3

Maybe it's your second command that is not quite right.

First, you must use apt full-upgrade (or dist-upgrade, it's the same) so that apt is allowed to automatically remove packages. This is needed here, because the packages mesa-va-drivers and mesa-vdpau-drivers will get removed (cf. changelog at https://salsa.debian.org/xorg-team/lib/mesa/-/blob/debian-unstable/debian/changelog).

Also, if you want to only upgrade some packages, you must run apt install PKG1 PKG2 ..., and not apt upgrade PKG1 PKG2 ... (I know, it's confusing),

The first command sudo apt update && sudo apt full-upgrade should have work... But I see in your apt output ... amazonaws.com bookworm .... If you mix Kali with another distro, then maybe that's the problem. Maybe you installed some packages that do not belong to Kali, and depend on mesa-va-drivers or mesa-vdpau-drivers, and now you can't upgrade because of that. I think that's your issue.

nah the '..... amazonaws.com bookworm .....' things is apt fetching updates for ngrok look at the 2nd line and when i use install this is the output

sudo apt install libegl-mesa0 libglx-mesa0 libegl-mesa0:i386 libglx-mesa0:i386 libgbm1 mesa-libgallium mesa-vulkan-drivers libgbm1:i386 mesa-libgallium:i386 mesa-vulkan-drivers:i386 libgl1-mesa-dri libgl1-mesa-dri:i386 
[sudo] password for syed: 
Solving dependencies... Error!  
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 mesa-libgallium : Breaks: mesa-va-drivers (< 25.2.8-3)
                   Breaks: mesa-va-drivers:i386 (< 25.2.8-3)
 mesa-libgallium:i386 : Depends: libllvm21:i386 (>= 1:21.1.0) but it is not going to be installed
                        Breaks: mesa-va-drivers (< 25.2.8-3)
                        Breaks: mesa-va-drivers:i386 (< 25.2.8-3)
 mesa-va-drivers : Depends: mesa-libgallium (= 25.2.6-1) but 25.3.2-2 is to be installed
 mesa-va-drivers:i386 : Depends: mesa-libgallium:i386 (= 25.2.6-1) but 25.3.2-2 is to be installed
 mesa-vulkan-drivers:i386 : Depends: libllvm21:i386 (>= 1:21.1.0) but it is not going to be installed
Error: Unable to satisfy dependencies. Reached two conflicting decisions:
   1. libllvm21:i386=1:21.1.8-1+b1 is not selected for install because:
      1. mesa-libgallium:amd64=25.3.2-2 is selected as an upgrade
      2. mesa-libgallium:amd64=25.3.2-2 Depends libllvm21 (>= 1:21.1.0)
      3. libllvm21:amd64 Breaks libllvm21:i386 (!= 1:21.1.8-1)
   2. libllvm21:i386=1:21.1.8-1+b1 is selected for install because:
      1. mesa-libgallium:i386=25.3.2-2 is selected as an upgrade
      2. mesa-libgallium:i386=25.3.2-2 Depends libllvm21:i386 (>= 1:21.1.0)
      3. libllvm21:i386 is available in version 1:21.1.8-1+b1

Ah Ok, I see that some kali-rolling, there are a version mismatch for libllvm21: amd64 has 1:21.1.8-1 and i386 has 1:21.1.8-1+b1. That breaks your use-case, and it's been reported on the Debian side: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124514

The amd64 package version 1:21.1.8-1+b1 is in kali-dev, so it will migrate to kali-rolling at some point. Unfortunately there's a rust and ocaml transition in kali-dev, and libllvm21 must migrate along. It means that we have to wait for all the automatic tests for ocaml and rust to run -- that must be around a thousand package or more. I think you'll still have to wait ~ 2 days or so before it's finally fixed in kali-rolling.

Alternatively, as a workaround, you could install the package libllvm21 from kali-dev, if you know how to configure apt for that.

I'll keep an eye on that to make sure it's fixed asap, but for now we have to wait for the tests to run...