feat(unzip,zipinfo): generate *.crx for Google Chrome Extension's ZIP archives

[akinomyoga]

See the commit message.

#1404 (comment)

I don't see a problem adding more of them. crx would fit in well if it's a zip, we have xpi already which is corresponding thing for Firefox.

#1404 (comment)

But re these, would be great to provide URLs to some sample files with which reviewers could verify that they work with these tools.

I've included the reference URL in the commit message as usual, but it might be harder to track the changes later because many extensions are included in a single line where git blame isn't useful to identify a commit that added a specific filename extension. Maybe we should include the reference information directly in the code comment inside the source code bash_completion. What do you think?

[akinomyoga]

The following commits have added filename extensions for unzip and zipinfo.

• 92f558d
• 3c3ab17
• fcaf3d4
• 29c8644
• 4c1cf9d
• 8273ce3
• 31b5cbc
• c263a3f
• df8bc32
• e5ee408
• 7b9dc46
• a576160
• f0a3147
• ca53345 (Note: this removed the code comment for the explanation on some filename extensions)
• 7c7b560
• 6a71ee5
• 8890abf
• 0ceca80
• 9566f59
• ba9cacc
• 9cbd3ce
• 95662ec
• 0b2be3f
• 82224e9
• b64e48a
• 5b55df4
• 7c16b79
• 63efd13
• 5fa59bc
• d1dfcfb
• c442af0

[scop]

Agree that git blame isn't too useful for these lines, but I think it's good enough if we clearly note each extension in the commit message. With the preceding dot it should be searchable enough from git log.

[scop]

LGTM, needs conflict resolution. Thanks!

[akinomyoga]

Thanks!