Default packagetype differs between `clone` and `sync` solution operations

The default --packagetype for pac solution clone is Both,
whereas the default --packagetype for pac solution sync is Unmanaged.

This feels inconsistent since I'm assuming that the intention is for sync to be used after an initial clone.

Clone

pac solution clone --help
Microsoft PowerPlatform CLI
Version: 1.19.4+gfbe2fd6

Error: A required argument --name is missing.

Usage: pac solution clone --name [--include] [--outputDirectory] [--async] [--max-async-wait-time] [--processCanvasApps] [--packagetype] [--targetversion]

[... snip ...]
  --packagetype               Specifies the extraction type for the solution. Can be: 'Unmanaged', 'Managed' or 'Both'; default: 'Both' (alias: -p)

Sync

❯ pac solution sync --help
Microsoft PowerPlatform CLI
Version: 1.19.4+gfbe2fd6

Error: An unknown argument --help was passed.

Usage: pac solution sync [--solution-folder] [--include] [--async] [--max-async-wait-time] [--processCanvasApps] [--packagetype]

[... snip ...]
  --packagetype               When unpacking/extracting, use to specify dual Managed and Unmanaged operation. When packing, use to specify Managed or Unmanaged from a previous unpack 'Both'. Can be: 'Unmanaged', 'Managed' or 'Both'; default: 'Unmanaged' (alias: -p)

Start with the pac solution clone and pac solution sync command entry points and trace how each sets the default --packagetype. Compare their help output and existing tests, if present. Done means the two operations use an intentional, consistent default and their help text accurately describes it.