Release tools - execute git commit --dry-run to prevent unexpected crashes

[pomek]

📝 Provide a description of the improvement

Our platform implements custom release tools. It allows for the preparation of the packages to be published on npm but also executes a dry run that produces packages but does not impact the repository (do not create a commit, a tag, etc.).

The dry-run mode is implemented by defining a skip callback:

ckeditor5/scripts/release/preparepackages.mjs

Lines 309 to 334 in b4759c7

	{
	title: 'Commit & tag phase.',
	task: ctx => {
	return releaseTools.commitAndTag( {
	version: latestVersion,
	files: [
	'package.json',
	`${ PACKAGES_DIRECTORY }/*/package.json`,
	`${ PACKAGES_DIRECTORY }/ckeditor5-build-*/build/**`,
	...ctx.updatedFiles
	]
	} );
	},
	skip: () => {
	if ( isNonCommittableRelease( cliArguments ) ) {
	return true;
	}
	// When compiling the packages only, do not commit anything.
	if ( cliArguments.compileOnly ) {
	return true;
	}
	return false;
	}
	}

While it worked and works fine in most cases, I think it isn't a proper approach as we miss execution of static analysis tools, like ESLint (attached as a pre-commit hook).

I would like to update our tools and processes:

• Git allows creating a commit in the dry-run mode. (ref)
• Verify and implement the dry-run mode in the commitAndTag() function.
• Update the Commit & tag phase. task in release tools. Instead of skipping it, pass the new flag.

Definition of Done

• commitAndTag() allows of creation of a new commit using the dry-run mode.
• The Commit & tag phase. task defines whether a commit should be done using the dry-run mode.
• All of our repositories using our tools are updated.