laminate on transfer

Nobody has claimed this yet.

Using the unifyfs_transfer call to transfer a file in from the real file system to unify, @craigsteffen found that the file was not being laminated. We likely will optionally want this to laminate files in unify after transferring a file in. Perhaps that could be added as an option to the unifyfs_transfer API?

For laminating a file after a transfer, I think we’d want to make a call to chmod() after calling the unifyfs_transfer_* functions here:
https://github.com/LLNL/UnifyFS/blob/a58c74c0e54911db4063e464526a8ddb7eb9ca8d/examples/src/transfer.c#L153

Or we could add an optional call to chmod() within the implementation of the unifyfs_transfer function itself:
https://github.com/LLNL/UnifyFS/blob/a58c74c0e54911db4063e464526a8ddb7eb9ca8d/client/src/unifyfs.c#L2808

And then once we get a unifyfs_laminate() call, the chmod() added here should be replaced.

Start with examples/src/transfer.c near line 153 and client/src/unifyfs.c near line 2808, tracing the unifyfs_transfer_* calls and current chmod behavior. Clarify whether the option belongs in the transfer API or example, and account for the future unifyfs_laminate() call; done should make the intended optional post-transfer lamination behavior explicit and tested.

Written by the indexing model from the issue text.