Prepare for v2 release

[Bobgy]

• Upgrade dependencies including licenseclassifier/v2 #203

The mass dep upgrade contained many breaking changes. Let's go for a v2.

Let's use master branch for v2.

TODOs:

• Fork v1 branch for archive
• Are there other breaking changes we wanted to do?
• Classify some new licenses that we don't know their types yet.
• Prepare a breaking change list.
• Performance Improvements #204
• Update import path.

Before ready

• Collect result diffence from v1 users.

[inteon]

@Bobgy any updates on when we can expect the v2 release?
We are pointing to the hash on master right now.

[Bobgy]

Welcome contributions again!
I no longer have enough time to work on this.

[damemi]

Talked to @Bobgy offline, we're going to start on the next steps of a v2 release with:

• Creating a v1 branch to preserve the current state (@Bobgy this should probably branch off at the commits before Upgrade dependencies including licenseclassifier/v2 #203 instead of the current master head right?)
• Update package/modules with /v2 following https://go.dev/blog/v2-go-modules

[Bobgy]

Just created a v1-branch to reserve v1 state.

[Bobgy]

@damemi We have 2 options to go v2 and I'm open to any one of them.

The v2 folder approach is the most compatible, yet I am not sure if that's necessary. Right now go-licenses pretty much assumes you are using go modules. We have a v1.0 version that's backward compatible with GOPATH if people still want to use GOPATH.

Simply changing the master branch as v2 can be simpler for maintenance.