Vector `INSERT` through SQL incorrectly allows vectors of different dimension and precision

It is possible to `INSERT` a vector with a different precision and dimensions than the ones defined in the schema.

Basically, this works, although it should not:

```sql
create table tHalfVector(a bigint, b vector(3, half), primary key(a))
insert into tHalfVector(100, !! v64 [1, 2, 3] !! )
```