Remove default from config_scripts payload_valid

[agrare]

Only set payload_valid if it was checked otherwise leave it as nil

ManageIQ/manageiq-providers-workflows#59 (comment)

[miq-bot]

Checked commit agrare@36c0807 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint
1 file checked, 2 offenses detected

db/migrate/20231114173829_remove_default_from_configuration_scripts_payload_valid.rb

• ❗ - Line 3, Col 5 - Style/MethodCallWithArgsParentheses - Use parentheses for method calls with arguments.
• ❗ - Line 7, Col 5 - Style/MethodCallWithArgsParentheses - Use parentheses for method calls with arguments.

[agrare]

ping @Fryguy

[miq-bot]

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s).

[kbrock]

ping. Is this ready?

[kbrock]

@Fryguy Is there a timeframe that is best to merge these schema PRs?

[Fryguy]

This one fell to the backburner, but I originally had concerns/thoughts around how to handle providers that don't support this column, and thus the value would be nil, and what that means (i.e. since nil is falsey, are they therefore invalid by default?)

[miq-bot]

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s).

[agrare]

@Fryguy how about we rename this payload_invalid so that the "unset" case isn't that the content is bad.