Internal: Performance improvements for `getConfig`

`getConfig` is currently a performance bottleneck and should be improved if possible.

Some ideas:

- Short-circuit esbuild generation if "nothing has changed"
- Do "optimistic file-checks" i.e. only check for file existence as part of error handling path to not slow down the critical path (e.g. when checking for existence of `contentlayer.config.ts`)
- Resolve Contentlayer version at compile time instead of dynamically
- Investigate ways to speed up the `import-compiled-contentlayer-config` step

Start by profiling getConfig, especially the import-compiled-contentlayer-config step and checks involving contentlayer.config.ts. Compare runs when configuration is unchanged and when error handling is triggered. Done means a measured improvement to the bottleneck while preserving existing configuration generation and error behavior.

Written by the indexing model from the issue text.