feat(lint): allow for custom commit parser function

This change makes it possible to pass a custom function to the top level
lint function, which is passed through to the parse function and
consequently passed through to the parser exposed by
convential-commits-parser. In linting it is important to parse content
to be linted with a high level of fidelity so linting can be applied
accurately. The default parser the is used, conventional-commits-parser
makes many assumptions about the format of the commit to perform its
parsing which leads to parsing errors and inaccuracies which in turn
lead to many false positives in linting, and incorrect or invalid errors
in additional confusing error messages.

This change will allow end users utilize a more accurate parser for
their linting purposes in the short term while issues with the default
parser are reconciled

Resolves: #4816

Author: esatterwhite

@commitlint/lint/src/lint.ts

@@ -37,7 +37,7 @@ export default async function lint(
 	const parsed =
 		message === ""
 			? { header: null, body: null, footer: null }
-			: await parse(message, undefined, opts.parserOpts);
+			: await parse(message, opts.parser, opts.parserOpts);
 
 	if (parsed.header === null && parsed.body === null && parsed.footer === null) {
 		// Commit is empty, skip

@commitlint/types/src/lint.ts

@@ -1,6 +1,7 @@
 import type { ParserOptions as Options } from "conventional-commits-parser";
 import { IsIgnoredOptions } from "./is-ignored.js";
 import { PluginRecords } from "./load.js";
+import type { Parser } from "./parse.js";
 import { RuleConfigSeverity, RuleConfigTuple } from "./rules.js";
 
 export type LintRuleConfig = Record<
@@ -15,6 +16,8 @@ export interface LintOptions {
 	ignores?: IsIgnoredOptions["ignores"];
 	/** The parser configuration to use when linting the commit */
 	parserOpts?: Options;
+	/** An optional custom parser function for parsing commit messages */
+	parser?: Parser;
 
 	plugins?: PluginRecords;
 	helpUrl?: string;