Create User-Dispatchable Workflow to Move Config Inputs

[CodeGat]

Currently, we require someone to login as tm70_ci to move configuration inputs into /g/data/vk83/configurations/inputs since it is restricted.

This is a bit painful, so create a workflow that takes in:

• Remote file source
• Remote file target
• Whether to overwrite the target with the source
• The ACLs that the file will have (create a sensible default)

Require sign off by developers, and log the inputs so we have visibility.

The workflow should copy source to target as tm70_ci and set appropriate ACLs.

Tasks

• [x] Do the above
• [ ] Also add inputs backup feature noted in https://github.com/ACCESS-NRI/model-config-inputs/issues/1

[CodeGat]

Per a conversation with @aidanheerdegen:

We should tack on the ability to store modified (created/updated/deleted) inputs on tape, in a structure like so:

input_backup/
├── 20240228/
│   ├── manifest.yaml
│   └── <update 1>
└── 20250101/
    ├── manifest.yaml
    └── <update 2> 

In which the datestamp subdirectory format is yet to be determined.

[CodeGat]

@aidanheerdegen I might need a hand regarding the commands for putting something on tape storage...