zvk: Check VR index alignment constraint and vm constraint

[YenHaoChen]

The vector specification requires aligning the VR index regarding the LMUL. Also, it requires that vd cannot be v0 when masking.

Although the vector crypto specification does not explicitly state those two constraints, the deriving extension should include the general constraints from the vector specification.

This commit checks the VR index and vm constraints on Zvk instructions.

[aswaterman]

@nibrunieAtSi5 @kdockser

[nibrunieAtSi5]

I think I tried to cover some of the missing alignment constraints in #1815.

I don't think this PR handles the scalar-element-group source register index alignment for .vs the way it should be (see riscv/riscv-isa-manual#1653): the vs2 operand alignment should not be checked against LMUL.

None of the vector crypto instruction working on element groups support masking.

[nibrunieAtSi5]

@YenHaoChen , could you help review #1815 ? It should fix the issues you intended to fix there (excluding the mask overlap which I believe is not an issue for any instruction working with element groups in vector crypto).

[YenHaoChen]

@nibrunieAtSi5
Before reviewing the PR, I need to familiarize myself with the vector crypto specification. Nevertheless, the behavior seems correct at a glance.

There are non-behavioral concerns in #1815. Reviewers would be much more willing to approve the PR if it could make the following modifications.

1. Usually, we expect each PR to deal with one thing. The PR implements two things. Perhaps, we can split it into two PRs, and reviewers could approve them separately.
2. Reviewers would be thankful if the contributor could squash and rebase their PR. Specifically, the second commit deletes all the codes from the first commit and adds different codes, confusing the reviewers. We may delete the first commit to help reviewers understand the PR. (Does the later commit delete all the code from the second commit again? I am unsure which commit contributes to the final code.)
3. Comments should go along with the code. Commits 61ad5bd and 0f1ef5c modify the comments only. Please squash the modification to the corresponding commits.
4. PR should not include typo correction of the PR itself. Please squash commits 636a5f3 and 494e219.