Fix for physical server alert bug

[skovic]

When deleting a physical infra provider, the delete may appear to be successful due to a message saying that the delete was successfully initiated; however, the delete actually fails with the following error in evm.log:

[----] E, [2018-08-09T16:16:47.588619 #9030:2ac60f3b5114] ERROR -- : MIQ(MiqQueue#deliver) Message id: [248], Error: [Could not find the inverse association for miq_alert_statuses (:physical_servers in MiqAlertStatus)]
[----] E, [2018-08-09T16:16:47.588971 #9030:2ac60f3b5114] ERROR -- : [ActiveRecord::InverseOfAssociationNotFoundError]: Could not find the inverse association for miq_alert_statuses (:physical_servers in MiqAlertStatus)  Method:[block (2 levels) in <class:LogProxy>]
[----] E, [2018-08-09T16:16:47.589098 #9030:2ac60f3b5114] ERROR -- : /usr/local/share/gems/gems/activerecord-5.0.7/lib/active_record/reflection.rb:202:in `check_validity_of_inverse!'

This PR fixes the bug by correcting the inverse_of specified in the PhysicalServer model's miq_alert_statuses relationship.

Fixes #17832

[skovic]

@miq-bot add_label bug

[skovic]

@agrare I found a bug related to the new physical server alert that was recently added. It actually causes the delete of a physical infra provider to fail. Can you take a look at this PR when you get a chance? Thanks

[miq-bot]

Checked commit skovic@694f304 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 👍

[agrare]

Thanks @skovic, FTR introduced by #17728