Use server: {} as standard configuration namespace

[pi0]

Currently in the docs we have lots of exceptions that Nuxt and Nitro config are different. This can be easily a case for any other meta framework.

Similar how vitest supports test key in vite config, we could do the same.

Our config loader could be smart to merge different sources and detect sub key usage for backward/forward compatibility.

[danielroe]

As a documentation improvement and convention (so Nuxt moves nitro -> server) I think it would make a lot of sense. 👍

(I don't think you mean this, but worth saying that I'm not a fan of Nitro resolving config from the Nuxt config file separately, though.)

[pi0]

Yeah no downstream logic to be in Nitro! It will make things just complexer i agree.