go.mod: bump operator-registry to v1.14.3 for bundle validation improvements

[joelanford]

Description of the change:
Bump operator-framework/operator-registry to v1.14.3.

Motivation for the change:
Resolves an issue with default channel bundle validation. The default channel label is not required.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

[dinhxuanvu]

/lgtm

[joelanford]

/hold

Need one more fix from operator-registry to get this to pass CI.

[joelanford]

/hold cancel

[jmrodri]

/lgtm

[jmrodri]

/lgtm

[joelanford]

/cherry-pick v1.0.x

[openshift-cherrypick-robot]

@joelanford: new pull request created: #3959

In response to this:

/cherry-pick v1.0.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[joelanford]

/cherry-pick v0.19.x

[openshift-cherrypick-robot]

@joelanford: #3953 failed to apply on top of branch "v0.19.x":

Applying: go.mod: bump operator-registry to v1.14.3 for bundle validation improvements
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 go.mod: bump operator-registry to v1.14.3 for bundle validation improvements
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick v0.19.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.