Problem: AMClient create package capability doesn't offer all the features of the package API endpoint

[ross-spencer]

Please describe the problem you'd like to be solved.

I'd like to be able to supply an accession number to the amclient library when initiating a transfer. E.g. it is useful for tests that we have written previously (bind pids). We need this if we want to migrate more tests to be API based and offer as much coverage as possible. Other users might need this to be able to utilize the API in its entirety through this wrapper.

Describe the solution you'd like to see implemented.

The parameters for the API are encoded here in amclient, and so we can add the remainder of the parameters that can be accepted by the API call to the package endpoint.

Additional context

This is simply an evolution of the capability offered by the client.

---

For Artefactual use:
Please make sure these steps are taken before moving this issue from Review to Done:

• All PRs related to this issue are properly linked 👍
• All PRs related to this issue have been merged 👍
• Test plan for this issue has been implemented and passed 👍
• Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍

[ross-spencer]

Related to item 13.3 in the current regression checklists then adding this feature to AMClient would make that automated test possible.