[Addon Dev] allow all of rollup's OutputOptions to be passed to addon.output()

[NullVoxPopuli]

Update!

This PR adds pass-through support for all of rollup's output options:

output: addon.output({ sourcemap: true });

Intellisense confirmed working, too:

---

(old PR description)

I found myself wanting to provide sourcemaps for libraries.
addon.output() does not allow for that, but you could do:

output: {
  ...addon.output(),
  sourcemap: true,
}

but, that's extra code on the consuming side, when it could just be 1 extra line of config in the new Addon part of the rollup config file.

There are a lot of output options tho: https://rollupjs.org/guide/en/#outputoptions-object.
🤷

Maybe instead, we can take any object as an argument to .output() and merge that in the rollup config?

[NullVoxPopuli]

I removed sourcemap from the constructor, kept the docs tho, and added all output options to the output function. Looks kinda fun (intellisense test):

kinda weird they don't have any description or anything on these, but that's work we PR to rollup to help everyone out

[ef4]

This PR comes down the difference between:

{
  // current
  output: { ...addon.output(),  sourceMap: true }
}

and

{
  // proposed
  output: addon.output({ sourceMap: true })
}

They're extremely close, but the proposed option forces you to read the documentation for addon.output() to understand what's going to happen, whereas the current option is Just Javascript™️ and it's transparent what's happening. So I'm not a fan.

[NullVoxPopuli]

aight, sounds good! 🥳