[Pre-RFC] `cargo package` should include fewer files by default

SwishSwushPow: > So in my opinion the issue of workspace licenses can be handled independently from the topic described in this Pre RFC and is not a prerequisite. Adding a glob-based license file matching to make a sensible selection of license files to include in a crate is not a short term, lukewarm solution to the issue of workspace licenses and is not influencing any decisions in that process. As soon as a solution is found for the workspace license issue, the glob matching of license files can be (and has to be) replaced by pulling in clear information about which license files need to go where, and I think that should be easily possible. During that step, crate authors have to make adjustments to their file structures anyway. But since currently most (if not all) workspaces have to rely on workarounds to correctly ship license files, the glob-based matching should be a fitting approach alongside it. Globbing wouldn't ever be a solution to the workspace license problem. However, solving workspace licenses means Cargo would have a definitive solution to knowing and bunding license files, making the globs obselete. That is what needs to be engaged with. I linked to issues not for the directly reported problem but the overlaps in use case and designs to make sure there is good alignment. While we may need to limit scope to move forward, we should consider the bigger picture to make sure we fit within it.