fix(types): directives without arguments but with modifiers

[lishixuan13]

fix #6427

<input v-model.trim="msg" />

/**
 * after compilation
 * 
 * [
 *    vModelText,
 *    msg.value,
 *    void 0,
 *    { trim: true }
 * ]
 */

error :

TS2322: Type '[ModelDirective<HTMLInputElement | HTMLTextAreaElement>, any, undefined, { trim: true; }]' is not assignable to type '[Directive<any, any>] | [Directive<any, any>, any] | [Directive<any, any>, any, string] | [Directive<any, any>, any, string, DirectiveModifiers]'.
  Type '[ModelDirective<HTMLInputElement | HTMLTextAreaElement>, any, undefined, { trim: true; }]' is not assignable to type '[Directive<any, any>, any, string, DirectiveModifiers]'.
    Type at position 2 in source is not compatible with type at position 2 in target.
      Type 'undefined' is not assignable to type 'string'.

[skirtles-code]

Looks good to me. Might be worth adding a test for this scenario to directives.spec.ts.

The original bug report was about webpack and compiler-generated code, but I believe this type change would also be useful when writing render functions directly with "strict": true. e.g. Playground.

[edison1105]

Thanks for the PR, but sorry, we saw this PR too late. This issue has already been fixed in #11540.
see #11540