Add suggestions to `vue/no-export-in-script-setup`

[chouchouji]

Tell us about your environment

• ESLint version: 8.44.0
• eslint-plugin-vue version: 9.17.0
• Vue version: 3.3.4
• Node version: 18.17.0

The problem you want to solve.

Can we add fixer to autofix this code for vue/no-export-in-script-setup rule?

Your take on the correct solution to problem.

Additional context

If you think so, I am pleased to submit a pr. Thanks!

[FloEdelmann]

In #2701, the rule was already improved to only report the export keyword for statements that might be relevant for local code, e.g.:

export const foo = 'bar'
console.log(foo)

As a potential follow-up improvement, a PR would be welcome that adds suggestions that remove the reported code (i.e. the whole statement for export * from 'foo' and only the export keyword for export const foo = 'bar'). For more context, see #2701 (comment).

Autofixes are considered too dangerous for this rule to break other code.