[Bug][compiler-v2] ability missing warning comes too late

[meng-xu-cs]

🐛 Bug

Compiling the following Move code with V2 compiler

module demo::demo {
    struct S<T: store> has store {
        field: T,
    }

    struct E<T: store> has store, drop {
        entry: S<T>,
    }
}

yields an error at the File Format generation phase:

bug: bytecode verification failed with unexpected status code `FIELD_MISSING_TYPE_ABILITY`. This is a compiler bug, consider reporting it.
  ┌─ /<redacted>/test/sources/test.move:1:1
  │  
1 │ ╭ module demo::demo {
2 │ │     struct S<T: store> has store {
3 │ │         field: T,
4 │ │     }
  · │
8 │ │     }
9 │ │ }
  │ ╰─^

Which is a bit late in the process.

With V1 compiler, the error message is more dev-friendly:

error[E05001]: ability constraint not satisfied
  ┌─ /<redacted>/test/sources/test.move:7:16
  │
2 │     struct S<T: store> has store {
  │            - To satisfy the constraint, the 'drop' ability would need to be added here
  ·
7 │         entry: S<T>,
  │                ^^^^
  │                │
  │                Invalid field type. The struct was declared with the ability 'drop' so all fields require the ability 'drop'
  │                The type '(demo=0x97751FCABB9A35CABA546D45C30E91CEB8B4622386C2DBF81B9B6D64A9F53AEF)::demo::S<_>' does not have the ability 'drop'

[wrwg]

This is the bytecode verifier as a verification step after code generation, and any error like this is definitely an unintended bug, though safe because the code can't be deployed.