[chip, dv] Some pad IO are forced in vseq

@sriyerg

The chip-level sysrst test directly forces the pad IO in this PR https://github.com/lowRISC/opentitan/pull/13216. I think it may be OK for now.
Once we update the pinmux configuration based on the actual use case, we should also clean up these forces.

Start with the chip-level sysrst test and PR 13216 to understand where the pad IO are forced in the vseq. Review the pinmux configuration for the actual use case, then remove the obsolete forces once that configuration is updated and verify the sysrst test still works.

Written by the indexing model from the issue text.