🔗 Linked issue

Resolves nuxt/nuxt#14604 and adds basic manifest implementing nuxt/nuxt#14605

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

When a major change in a project happens (such as updating nuxt or renaming directory) we most likely need to invalidate caches to avoid unpredictable behavior. This PR does two things:

• Write a basic nuxt.json to buildDir/.nuxt only for nuxi dev (1)
• Checks manifest hash (full hash) against the previous build and call nuxi cleanup in case of hash mismatches.

Remarks:

• I've not included more extensive manifest info and hashes unless we find initial change is not enough. As mentioned by @danielroe in clean up up cache dirs on rootDir/hash change nuxt#14604, bundlers (vite and webpack) also handle cache invalidation for dependencies
• We probably need to generate two separate manifests for dev and prod (Split dev and production output inside buildDir nuxt#14607)
• It only invalidates caches for nuxi dev and not nuxi build because i don't believe we saw any cache issue on nuxi build. We can add later on to both commands and utils are already refactored to prepare for this.

(1) Sample .nuxt/nuxt.json:

{
  "_hash": "AQBCqiYugT",
  "project": {
    "rootDir": "/Users/pooya/Code/framework/playground"
  },
  "versions": {
    "nuxt": "3.0.0-rc.8"
  }
}

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.