[DOCS] Add complete third-party license documents

[hesreallyhim]

Fixes #121

In this PR:

• Added sub-directory under top-level marketplace directory with plugin-level attribution information for all third-party authors (as is required by those licenses).
• Added this same documentation under the cli/commands structure. (It isn't exactly clear to me how this repo/marketplace is structured, so I wasn't sure where this belonged, and Anthropic has not provided any clear guidance for how to include third-party attributions into a plugin or marketplace manifest/json. My reasoning for putting it in both places is that (as far as I can grasp) these are two independent ways in which third-party resources are distributed, and so each of them ought to include the original license information in order to be compliant. A general statement that certain resources are due to third-party authors is not legally sufficient. In any case, if having it in both places is redundant, you may of course feel free to structure it however you think is best.)
• Minor edit to the text in README regarding Hobson and myself - feel free to edit - I added one sentence to acknowledge my contribution in this respect, and removed the existing line (Please note that **awesome-claude-code** is **no longer licensed under CC 1.0**.) which kind of made it sound a little negative IMO.
• Most of this documentation work was done with the help of Claude Code web so I just included all of the "research" that it did under the ATTRIBUTION_DOCS directory only so that you can see what the reasoning process was (which, in my cases, was probably not entirely accurate, and you can see that I did not attempt to "investigate" any additional issues that it probably incorrectly flagged, so I don't endorse those documents as "evidence" of anything). My assumption/intention was that you would delete that directory, and I only include it in this PR to show you exactly what went into it. If any of the individual links/attributions to individual authors are not correct, you can examine the "thought process" and of course only you can know where they came from. So, again, just to be clear, that directory was intended to be deleted before merging, and is included just for your benefit.
• One final word of caution - I'm not an expert so I can't give you any advice, but the non-MIT licenses that are on the awesome-list may not be compatible with inclusion in this project (copyleft), but I'll leave that to you, I think adopting these changes would already go a long way towards improving the open source ecosystem.

I appreciate your enthusiasm for adopting these changes, bearing in mind that it's not only a matter of showing respect and giving credit, but it's actually a legal obligation, as stated in the license documents themselves, so this is also an effort to improve the legal integrity of your marketplace. I know this type of practice is not always common, but in my opinion it's really important, especially when you consider what people are going to do with your repo downstream, and all the marketplaces that are already just copying everything you've done and putting it under their own brand, so showing that these licenses carry significance and impose legal requirements is in everyone's interest, I think. Let me know if you have any more thoughts, and thank you for taking these concerns into account.

EDIT: FWIW, I have also reached out to Anthropic and formally requested that they make some changes to the documentation about Marketplaces so that everybody knows what restrictions open source licenses in fact carry, as I think it's more a matter of misinformation than willful "theft" of other people's work (although there are definitely some bad actors doing that already). People like you and other well-regarded authors can do a great service by adopting these kinds of practices and demonstrating to others that open source contributors still have legal rights. All the best.

[vercel[bot]]

@hesreallyhim is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.