fix: default sideEffect option is delivered to rollup

[XiSenao]

Description

fix: #15660

Additional context

I think the priority of sideEffect in package.json is higher than the moduleSideEffects configuration in rollup, and the configuration takes precedence over the default value true. When the sideEffect option is not specified in package.json, pass null value to rollup. rollup will determine the value of moduleSideEffects based on the treeshake.moduleSideEffects configuration item or a fallback default value of true.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines, especially the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Update the corresponding documentation if needed.
• Ideally, include relevant tests that fail without this PR but pass with it.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[bluwy]

Makes sense to me. It seems to be what @rollup/plugin-node-resolve does too: https://github.com/rollup/plugins/blob/2a19079892f0bef53b557da965339cdef0a13a93/packages/node-resolve/src/util.js#L100