Fixes #39374 - Add missing ipmi_boot parent permission mapping for taxonomy-scoped requests

[spesnova717]

Summary

Fixes an unknown parent permission for api/v2/hosts#ipmi_boot error that occurred when calling hammer host boot with --organization-id and --location-id. The root cause was a missing ipmi_boot entry in the parent permission mapping of Api::V2::HostsController.

Background

When a taxonomy context is present, the authorization path differs from the default flow. Because ipmi_boot was not registered in the parent permission map, the permission resolution failed, causing the request to be rejected. Requests without taxonomy options succeeded as expected.

Changes

• Added ipmi_boot to the parent permission mapping in Api::V2::HostsController
• Added a regression test to verify that boot API calls succeed when taxonomy context is provided

Reproduction & Verification

1. Failing case
   hammer host boot --id 3 --device bios --organization-id 1 --location-id 2
2. Passing case (no taxonomy)
   hammer host boot --id 3 --device bios
3. After the fix, both commands return 200 OK. Regression test passes in CI.

Expected outcome

Eliminates the unknown parent permission for api/v2/hosts#ipmi_boot error that only appeared when taxonomy options were specified.