Move lock message inputs from inline to actions cart

[tameremad]

The aim of this PR is to make locking an application or environment simpler. Most use cases include adding multiple locks at the same time (with the same message). So by moving the input field to the cart, the locking process is simpler for the users.

The BatchAction type is generated from the API proto file directly. This type includes a create...(env/app)...Lock. which was used to represent lock actions in the Cart.

After moving the input field, the lock button has to add lock actions to Cart without any lock message. which creates a problem because the message field is required for BatchAction but it's not yet available.

To solve it, This PR will:

• Create a new Type Union of all the different actions, namely, CartAction, and then use it to represent different actions in the frontend.
• Remove the input fields from ReleaseDialog/LockButtonGroup and from ReleaseDialog/CreateLockButton
• Use CartAction instead of BatchAction in Warnings, Releases, ReleaseDialog, ActionsCart, and index.tsx.
• Create a new file ActionDetails that contains the CartAction type, and the function to transform CartActions to BatchActions before sending the API request.
• Move getActionDetails, ActionTypes from ConfirmationDialog to ActionDetails
• Add an input field in CheckoutDialog that appears only when the cart contains create-lock actions. use this input as the lock message.
• Add tests in ActionDetails.test and modify the tests of CheckoutDialog.test and ConfirmationDialog.test to use CartAction
• Create an issue for more improvement points from this PR: Collection of small improvements. #195

[fdcds]

Some more comments.