object store `put` does not obey `content-disposition` option for multipart uploads

How to reproduce:
Upload something small:

oci os object put --bucket-name BUCKET --file SOME_FILE_BELOW_128MB --name SOME_NAME --content-disposition attachment --force --region us-ashburn-1 --content-type 'text/plain'

Get the headers of that file:

curl -I https://objectstorage.us-ashburn-1.oraclecloud.com/...   
HTTP/1.1 200 OK
accept-ranges: bytes
...headers omitted...
content-disposition: attachment

This look s fine.
Now upload a large file:

oci os object put --bucket-name BUCKET --file SOME_FILE_ABOVE_128MB --name SOME_NAME --content-disposition attachment --force --region us-ashburn-1 --content-type 'text/plain'

Get the headers of that file:

curl -I https://objectstorage.us-ashburn-1.oraclecloud.com/...   
HTTP/1.1 200 OK
accept-ranges: bytes
... content-disposition is missing!

I am currently working around the issue by adding --no-multipart option to the oci command line, but this is obviously not ideal.

Start at the oci os object put command and trace how --content-disposition is handled when multipart upload is selected; compare it with the --no-multipart path. Reproduce the issue with files below and above 128 MB, then verify that both uploads include the content-disposition header.