Integrate go-dag-jose plugin

[smrz2001]

Integrate go-dag-jose plugin

Description

This PR integrates the go-dag-jose plugin into IPFS.

How Has This Been Tested?

• ipfs dag put --store-codec dag-jose and ipfs dag get work correctly
• All IPLD dag-jose fixtures work correctly

Definition of Done

• My code follows conventions, is well commented, and easy to understand
• My code builds and tests pass without any errors or warnings
• I have tagged the relevant reviewers
• The changes have been communicated to interested parties
• Use the released version of go-dag-jose

References:

• feat: dag-jose implementation using IPLD schema/code generation ceramicnetwork/go-dag-jose#23

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[warpfork]

@aschmahmann suggests that we should also add a smoke tests that all the wiring works, by using a sharness test: https://github.com/ipfs/go-ipfs/blob/master/test/sharness/t0280-plugin-git.sh is an example for git. Can we quickly add something similar for this?

[smrz2001]

@aschmahmann suggests that we should also add a smoke tests that all the wiring works, by using a sharness test: https://github.com/ipfs/go-ipfs/blob/master/test/sharness/t0280-plugin-git.sh is an example for git. Can we quickly add something similar for this?

Had to wrangle bash into submission so took a little longer than I expected. Please take a look @aschmahmann and @warpfork.

Also, I do see the failing CI tests so will work on fixing them ASAP.

[BigLep]

@smrz2001: @aschmahmann is going to rebase first since it's quite possible the CI failures aren't your fault. It looks like you may have forked at an inopportune time while we were getting interoperability tests to pass.

[aschmahmann]

@smrz2001 I don't have permissions to push to your branch can you give me permissions (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) or do the rebase yourself?

[smrz2001]

Thanks, @BigLep.

Hey @aschmahmann, just looking at this. I can't find that checkbox for some reason 😕 Give me a couple min to figure this out, otherwise I'll try the rebase myself.

[smrz2001]

omfg, I hate WSL (Windows Subsystem for Linux) sometimes. One of the submodules keeps messing up my attempts to do anything because it shows up as a diff when there is none.

I just added you to my fork, @aschmahmann.

[stbrody]

🥳 🎉

Thanks @aschmahmann for the quick turnaround!