fix: use `turbopack.root` value for `outputFileTracingRoot` to have consistent tracing root (#82653)
Regressed from https://github.com/vercel/next.js/pull/82164
Previously, `outputFileTracingRoot` was always set via `findRoot()` if
the option was not explicitly given. However,
https://github.com/vercel/next.js/pull/82164 changed the behavior to run
`findRoot()` only if neither `outputFileTracingRoot` nor
`turbopack.root` was given.
Modified to:
- When BOTH options are given, ensure they match, or else WARN and use
`outputFileTracingRoot`.
- When EITHER option is given, map the other value as the other.
- When NONE is given, call `findDir()` and use its value.
- After the processes above, if the root dir value is not assigned,
throw an error as a Next.js bug.
Fixes https://github.com/vercel/next.js/issues/82626