Fixes #36581 - Treat indeterminate/nil needs_publish as true in the API

[sjha4]

What are the changes introduced in this pull request?

When users pass true for publish-only-if-needed param, we should let them publish cv where needs_publish? value is indeterminate(nil). This is consistent with UI behavior where we don't provide a notice to users when publishing a CV if needs_publish is true/indeterminate.

Considerations taken when implementing this change?

What are the testing steps for this pull request?

1. Create a CV.
2. Publish.
3. hammer -r content-view publish --id $id --publish-only-if-needed true
4. You will see a message saying no changes to publish.

Could not publish the content view:
  Content view does not need a publish since there are no audited changes since the last publish. Pass check_needs_publish parameter as false if you don't want to check if content view needs a publish.

5. In console, run Audit.delete_all . This creates the indeterminate state for us where we lose audits of all changes.
6. Publish from hammer with command above. It should let you publish CV.

[theforeman-bot]

Issues: #36581

[sjha4]

[test katello]

[chris1984]

ACK, works great.

[vagrant@centos7-hammer-devel ~]$ hammer -r content-view publish --id 2 --publish-only-if-needed true
Could not publish the content view:
  Content view does not need a publish since there are no audited changes since the last publish. Pass check_needs_publish parameter as false if you don't want to check if content view needs a publish.