chore: move shouldMergeCompilationJobs call to the build system

[galargh]

• Because this PR includes a bug fix, relevant tests have been included.
• Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
• I didn't do anything of this.

---

We should call shouldMergeCompilationJobs only if BuildOptions.mergeCompilationJobs parameter wasn't passed to the build system explicitly.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4909f3f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
hardhat	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 3, 2025 10:14am

[kanej]

To confirm my understanding. Instead of saying that invocations of the build system's build should set a bool on merging compilation jobs at each invocation site; we switch to there being a default behavior that matches the current two invocations?

[galargh]

Yes, exactly! I want the shouldMergeCompilationJobs(buildProfileName) to become the default. The users of build() would still be able to set the mergeCompilationJobs bool option if they so choose.

[kanej]

I think this makes sense given that we pass in the buildProfile.