Refactor upload-bin handler to reuse more of SDK built-in functionality

[AnnaShaleva]

Is your feature request related to a problem? Please describe.

upload-bin has code that manually constructs object before uploading it to NeoFS:

neo-go/cli/util/upload_bin.go

Lines 593 to 616 in 6a7d2bc

	ownerID.SetScriptHash(owner)
	hdr.SetPayload(objData)
	hdr.SetPayloadSize(uint64(len(objData)))
	hdr.SetContainerID(containerID)
	hdr.SetOwnerID(&ownerID)
	hdr.SetAttributes(attrs...)
	hdr.SetCreationEpoch(1)
	v.SetMajor(1)
	hdr.SetVersion(v)
	if !homomorphicHashingDisabled {
	checksum.Calculate(&chHomomorphic, checksum.TZ, objData)
	hdr.SetPayloadHomomorphicHash(chHomomorphic)
	}
	checksum.Calculate(&chSHA256, checksum.SHA256, objData)
	hdr.SetPayloadChecksum(chSHA256)
	err := hdr.SetIDWithSignature(signer)
	if err != nil {
	return resOID, err
	}
	err = hdr.CheckHeaderVerificationFields()
	if err != nil {
	return resOID, err
	}

Describe the solution you'd like

NeoFS SDK already has a proper object construction code, we need to reuse it.

Describe alternatives you've considered

Keep it as is, depends on the result of #3652.

[AliceInHunterland]

Only after nspcc-dev/neofs-node#2721 (comment) and resolved nspcc-dev/neofs-node#2990, because such "improper" usage of NeoFS is intended to prevent duplicates. Currently, we can only have duplicates because of partially completed search results. Such object creation reduces the likelihood of duplicates with the current search version.

[AnnaShaleva]

Ref. #3654 (comment).