Fixes #34182 - fix error message when import attribute is missing

[evgeni]

What are the changes introduced in this pull request?

Corrects error message when there are import attributes missing.

Otherwise you get the following error:

undefined local variable or method `import_attributes' for #<Katello::Api::V2::RepositoriesController:0x000055ecb351d600>
Did you mean?  import_attribute

Or, fixing that:

wrong number of arguments (given 2, expected 1)

Instead of e.g. "ostree_repository_name is required"

Considerations taken when implementing this change?

None, I just want the error to be correct ;-)

What are the testing steps for this pull request?

Trigger import_uploads for an OSTree content w/o setting ostree_repository_name

[theforeman-bot]

Issues: #34182

[evgeni]

I do wonder why RepositoryControllerTest::test_import_uploads_ostree_fails_without_required_params didn't catch that?!

Oooh, it's skipped. Should it not be skipped anymore? We'll find out in #9863

[evgeni]

Error Message

Expected response to be a <422: Unprocessable Entity>, but was a <500: Internal Server Error>...

Stacktrace

Failure:
test_import_uploads_ostree_fails_without_required_params(Minitest::Result) [/home/jenkins/workspace/katello-pr-test/test/controllers/api/v2/repositories_controller_test.rb:993]:
Expected response to be a <422: Unprocessable Entity>, but was a <500: Internal Server Error>
Response body: {"displayMessage":"undefined local variable or method `import_attributes' for #\u003cKatello::Api::V2::RepositoriesController:0x0000000017ec0da8\u003e\nDid you mean?  import_attribute","errors":["undefined local variable or method `import_attributes' for #\u003cKatello::Api::V2::RepositoriesController:0x0000000017ec0da8\u003e\nDid you mean?  import_attribute"]}.
Expected: 422
  Actual: 500

Now we're talking!

[evgeni]

Right, so I can't enable the controller test w/o offending all the recorded VCR tapes. And I am more in 🎄 than in 📼 mood ;)

[evgeni]

error is during assets precompile, which is unrelated

[jlsherrill]

ACK for the code change, should we open a new issue so we can more easily backport the issue?

[jlsherrill]

[test katello]