redfish_command: Add OemParameters support in MultipartHTTPPushUpdate

[cwhuang]

Summary

AMI BMC requires an additional OemParameters json when doing MultipartHTTPPushUpdate updates. It looks like #7331 but not exact the same. AMI BMC needs the OemParameters to be a separate json file instead of a key/value in UpdateParameters.
We suggest to add an option update_image_type to address it.

Issue Type

Feature Idea

Component Name

redfish_command

Additional Information

Presumably it would be used like:

- name: Multipart HTTP push with additional options
  community.general.redfish_command:
    category: Update
    command: MultipartHTTPPushUpdate
    baseuri: "{{ bmc_host }}"
    username: "{{ bmc_user }}"
    password: "{{ bmc_password }}"
    timeout: 600
    update_image_file:  bmc-image.ima
    update_image_type: BMC
    update_targets: /redfish/v1/UpdateService/FirmwareInventory/BMCImage1

### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct

[cwhuang]

I have worked out a patch to support it. Test OK with AMI BMC 13.3.
If you agree I'll send the pull request.

[ansibullbot]

cc @TSKushal @Bhavya06 @jyundt @mraineri @rajeevkallur @renxulei @tomasg2012 @xmadsen
click here for bot help

[sseekamp]

@cwhuang are you sure that's the not the behavior that's present? My original PR referenced above was for an AMI BMC system as well. Do you need an additional "upload file" definition?

community.general/plugins/module_utils/redfish_utils.py

Lines 1947 to 1949 in e5ab4be

	multipart_payload = {
	'UpdateParameters': {'content': json.dumps(payload), 'mime_type': 'application/json'},
	'UpdateFile': {'filename': image_file, 'content': image_payload, 'mime_type': 'application/octet-stream'}