feat: support useless literal object expansion

[ahaoboy]

const b = {};

const a = {
  ...{
    x: false,
  },
  ...b,
};

oxlint

const b = {};

const a = {
  x: false,
  ...b,
};

[0f-0b]

There are some edge cases related to __proto__ and super. For example, the expression { ...{ __proto__: null } } is not equivalent to { __proto__: null }. Neither is { ...{ method() { return super.constructor } } } interchangeable with { method() { return super.constructor } }.

[ahaoboy]

There are some edge cases related to __proto__ and super. For example, the expression { ...{ __proto__: null } } is not equivalent to { __proto__: null }. Neither is { ...{ method() { return super.constructor } } } interchangeable with { method() { return super.constructor } }.

It seems that oxlint has not considered this much, and this seems more suitable as a warning to remind users that there may be unnecessary overhead

const b = {};

const a = {
  ...{
    x: false,
  },
  ...b,
};

const a2 = {
  ...{
    __proto__: null
  },
  ...b,
}

const a3 = {
  ...{
    method() { return super.constructor }
  },
  ...b,
}

const b = {};

const a = {
  
    x: false,
  ...b,
};

const a2 = {
  
    __proto__: null,
  ...b,
}

const a3 = {
  
    method() { return super.constructor },
  ...b,
}