Creating PhysicalChassis controller and adding endpoint configuration

[EsdrasVP]

This PR adds:

• GET /api/physical_chassis
• GET /api/physical_chassis/:id
• POST /api/physical_chassis (action: refresh)
• POST /api/physical_chassis/:id (action: refresh)

Depends on:
ManageIQ/manageiq#17320 [Merged]
ManageIQ/manageiq-api#364 [Merged]

[abellotti]

without this PR you can still access them as a relationship, i.e. GET /api/providers/:id?attributes=physical_chassis. Is the /api/physical_chassis or formal subcollection i.e. GET /api/providers/:id/physical_chassis needed ? If so you'd need an miq product feature identifier for it (manageiq/db/fixtures/miq_product_features.yml) so we can specify the :identifier: entries in the api.yml accordingly (RBAC purposes). Thanks.

[EsdrasVP]

@abellotti Thank you for the reminder. I put all the necessary identifiers in api.yml and miq_product_features.yml for both GET and POST features.

[abellotti]

ping @EsdrasVP can you revisit ? looks like the dependent PRs were merged.

[miq-bot]

Checked commits EsdrasVP/manageiq-api@d139c72~...ddbbc82 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 1 offense detected

app/controllers/api/physical_chassis_controller.rb

• ❗ - Line 26, Col 5 - Style/RescueStandardError - Avoid rescuing without specifying an error class.

[EsdrasVP]

@abellotti I revised and now both code climate and travis are passing.

[abellotti]

Thanks @EsdrasVP for the API Enhancement. LGTM !! 👍