broadcom/compiler: remove v3d_fs_key depth_enabled field.

It is not used right now, so keeping it adds some noise/confusion.

So far configuring Z test are done through the CFG_BITS. See
v3dX(emit_state) at v3dx_emit.c for v3d, and pack_cfg_bits at
v3dv_pipeline.c for v3dv. There flags like z_updates_enable and others
are filled up.

That key field seems like a leftover coming from using vc4 as
reference, as that driver defines and uses a field with name name.

Reviewed-by: Iago Toral Quiroga <itoral@igalia.com>
Part-of: <!7421>
35 jobs for master in 26 seconds (queued for 2 seconds)
Status Job ID Name Coverage
  Container
manual #5356718
aarch64 manual
arm_build
manual #5356719
manual
arm_test-base
passed #5356720
git_archive

00:00:18

manual #5356715
manual
x86_build-base
manual #5356717
manual
x86_build_old
manual #5356716
manual
x86_test-base
 
  Container 2
created #5356728
android_build
created #5356731
arm64_test
created #5356725
i386_build
created #5356721
kernel+rootfs_amd64
created #5356722
aarch64
kernel+rootfs_arm64
created #5356723
aarch64
kernel+rootfs_armhf
created #5356726
ppc64el_build
created #5356727
s390x_build
created #5356724
x86_build
created #5356729
x86_test-gl
created #5356730
x86_test-vk
 
  Sanity
passed #5356732
check mr

00:00:07

 
  Meson X86 64
created #5356738
meson-clang
created #5356737
meson-classic
created #5356739
meson-clover
created #5356734
meson-clover-testing
created #5356735
meson-gallium
created #5356736
meson-release
created #5356733
meson-testing
created #5356740
meson-vulkan
 
  Scons
created #5356741
allowed to fail
scons-win64
 
  Meson Misc
created #5356742
meson-android
created #5356744
aarch64
meson-arm64
created #5356745
aarch64
meson-arm64-build-test
created #5356743
aarch64
meson-armhf
created #5356746
meson-i386
created #5356749
meson-mingw32-x86_64
created #5356748
kvm
meson-ppc64el
created #5356747
kvm
meson-s390x