Specs use case insensitive fqname for comparison

Automation engine uses lowercase names for domains, namespaces
class, instances and methods. It can be refered to in mix case in
the models. The fqname is critcal to locating files in the new
git based automated model, by having mixed case the search takes
longer so we are planning on using all lowercase name when storing
files in git and the fqname becomes all lowercase.
This method name doesn't evoke that an assertion/expectation is being made.  We typically prefix methods that do that with assert_, so perhaps `assert_string_array_ignorecase`.

A completely alternate suggestion, which is also more reusable, is to make a custom matcher, as these tend to be more rspec-ish.

Then the caller would do something like the following:

```ruby
expected = %w(/DOM2/A/b/C/cLaSS1/method1 /DOM1/A/B/C/CLASS1/method1 /DOM3/a/B/c/CLASs1/method1)
actual = MiqAeMethod.get_homonymic_across_domains('/DOM1/A/B/C/CLASS1/method1', true).collect(&:fqname)
expect(expected).to match_array_ignoring_case(actual)
```