fix(vm): remove nonexistent vesting static precompile

[nowooj]

Description

This PR removes the nonexistent vesting static precompile address from the default active static precompile list.

The vesting precompile address was listed in AvailableStaticPrecompiles, but there is no precompiles/vesting implementation and no corresponding static precompile registration in DefaultStaticPrecompiles. This could make 0x0000000000000000000000000000000000000803 active in params without a registered implementation.

Closes: #1192

---

Author Checklist

I have...

• tackled an existing issue or discussed with a team member
• left instructions on how to review the changes
• targeted the main branch

Review instructions:

• Confirm 0x0000000000000000000000000000000000000803 is no longer included in default/manual active static precompile lists.
• Confirm existing precompile addresses are not renumbered.
• Confirm tests pass with go test -tags=test ./x/vm/types ./x/vm/keeper.

[greptile-apps]

PR author is not in the allowed authors list.

[aljo242]

this is the right pr to merge over #1196 (more complete, covers genesis scripts too). one concern before merge:

no param migration. any chain initialized with default params already has 0x0000000000000000000000000000000000000803 in active_static_precompiles state. if ValidateBasic checks enabled precompiles against AvailableStaticPrecompiles, those chains will fail param validation on upgrade. needs a migration to strip the address from existing state, or confirmation that it is safe to skip.

[aljo242]

needs param migration for existing chains that already have the vesting precompile address in state.