Improve Naming for Swift Packages using Package.resolved v2

[bennokress]

Problem (Issue #179)

With the new Package.resolved JSON version 2 (#174), which Apple introduce with Xcode 13.3 and Swift 5.6, I miss the correct package names.

Attempted Solution

Based on the idea of @ykws:

We may be able to pick up the name from Package(name:) in Package.swift, we can access each location in Package.resolved as repository url.

This PR has a solution that works in most cases by doing exactly that and falls back to a sensible default name when parsing the Package.swift fails.

In depth

What I implement here is a 3-step process to get the best name possible from the new version of Package.resolved:

1. Make sure we don't parse a Package.resolved v1 file and instantly return the name from that otherwise (current v1 implementation)
2. Take the Repository Name from the Github Conversion Step that is currently implemented in LicensePlist which is already an improvement on the result of Step 1 (current v2 implementation), since it has uppercased characters in all the right places. We still have some issues when dealing with Packages containing spaces though (those have dashes instead, but replacing those would break Packages that really have dashes in their names).
3. Parse the Package.swift from the Repository by looking for the first Package object, removing all nested code inside [...] to eliminate dependency and target names and finally getting the remaining value for name. If anything fails we return nil which lets us fall back to the result of Step 2.

Edge cases I encountered are also added as Unit Tests, so you can play around in the parser with confidence.

[mono0926]

Thanks, released: https://github.com/mono0926/LicensePlist/releases/tag/3.22.2