Attach an uploaded file to a drive item

Turns bytes you have already uploaded into a file on the drive item named in the path, and returns it in the detail view. upload_id is the only key this accepts: create a ticket with POST drive-items/{drive_item}/uploads, PUT the raw bytes to its upload_url, then send its id here. Everything about the file (its name, size, media type, collection and storage location) is read off the ticket and off the bytes that actually arrived, so file_name, mime_type, byte_size, collection and disk are all a 422. The file lands in the document's attachments collection; content belongs to the editor and file is the document's own payload, so neither can be written here. The ticket must have been created for this drive item, by this API token, and must not have expired or been registered already. The declared permission is project_drive::create; customer_drive, organization_drive and user_drive apply by owner type, and the record rule requires edit access: read access to a document is not enough to attach to it, which is deliberately stricter than plnnrly. Attaching additionally requires project_management::manage_work_items for the file itself. An archived document is 404. Idempotency-Key is required: a lost 201 retried without one would report a failure for a create that succeeded. There is no Location header (a file has no item URL of its own), and no PATCH or DELETE on a file; remove one in plnnrly.