Fixes bulk checking out of undeployable asset

[Godmartinz]

This prevents bulk checking out assets with an undeployable status. Redirecting you back to the asset index.

Plural:

Singular:

#16455

[what-the-diff]

PR Summary

• Enhanced asset checkout process

  • This update includes a new feature that prevents the bulk checkout of assets that are listed as undeployable. If an attempt is made to checkout such assets, an error message will be displayed. This improvement ensures that only assets that are available for deployment can be checked out, thereby streamlining the system's operation.

• Improved language handling

  • Updates on the language file form.php introduces an additional translation entry. This will display a translated message when undeployable assets are included in a bulk checkout request. This feature adds more clarity to the user experience, particularly for non-English speaking users and enhances the system's overall accessibility.

[snipe]

I think we wouldn't want to allow an archived asset to be checked out?

I think there's a small conflict in a few of the ways we handle this, which we should probably address, since the behavior is different in a few spots. In the API Statuslabel checkIfDeployable() method, we allow pending or deployable. (That is only used by the create/edit asset form when determining if we should present a checkout, via #16354)

In the query scopes on the Asset, scopeRTD(), scopeUndeployable(), we include/exclude pending. We should probably make those consistent across the board, but we'd need to see what else it might break before doing that.

[snipe]

Sorry, the double negatives are killing me here lol

[snipe]

I think deployable = 0, archived = 1 is all we need here?

I dunno, now I'm confused :-/