feat(cli): pass a context when nuxt.config exports fn

[pimlie]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Pass a context when nuxt.config exports a function. Context lists the command name (eg build, dev, start) and a dev boolean.

Note: using the term context might be confusing as this is ofc not the normal Nuxt context people are used to. Not sure how to call it differently though

Example usage:

// nuxt.config.js
export default ({ command, dev }) => {
  return {
    
  }
}

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[codecov-io]

Codecov Report

Merging #6855 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6855   +/-   ##
=======================================
  Coverage   64.76%   64.76%           
=======================================
  Files          78       78           
  Lines        2722     2722           
  Branches      708      708           
=======================================
  Hits         1763     1763           
  Misses        730      730           
  Partials      229      229

Flag	Coverage Δ
#unit	64.76% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 154fd73...8651b6d. Read the comment docs.