Fix issue: panic when using custom matchers

[nunnatsa]

Description

custom matchers that are defined in other packages, and get no parameters, cause panic, ans they wrongly treated as the MatchError matcher.

Custom matchers that are defined in other packages, and get some parameters, may cause false positive for wrong usage of MatchError matcher.

This PR fixes this issue.

Fixes #124

Type of change

Please delete options that are not relevant.

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] Added test case and related test data
• [ ] Update the functional test

Checklist:

• [x] I have performed a self-review of my own code
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [X] Any dependent changes have been merged and published in downstream modules
• [x] I ran golangci-lint

@nunnatsa

[github-actions[bot]]

Pull Request Test Coverage Report for Build 7272279591

• 19 of 21 (90.48%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.3%) to 84.786%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
ginkgo_linter.go	19	21	90.48%
<!--	Total:	19	21	90.48%	-->

Totals
Change from base Build 7244526420:	0.3%
Covered Lines:	1109
Relevant Lines:	1308

---

💛 - Coveralls