chore: run yarn lint

[rootulp]

While working on a different PR, the commit pre-hook failed because yarn lint resulted in a diff. Since these changes are unrelated to my PR, I included them here.

Note: I wonder why CI lint didn't catch these? Do we want an issue to investigate the discrepancy between local lint and CI lint?

[jcstein]

I had this happen to me and added the linting in a PR I have open (not best practice), so thanks for opening this. Just reverted the commit on that PR.

Note: I wonder why CI lint didn't catch these? Do we want an issue to investigate the discrepancy between local lint and CI lint?

It doesn't look like there is a CI lint on the most recent PRs...so looking into that now.

Regardless, I think that we do need to look into the flow of the linting with the pre-commit hook, and whether it should also exist the same way as CI, as I don't see it running on this PR? As for now, it only is used if developer downloads dependencies, otherwise husky won't run the pre-commit EDIT: i think that I took off the CI check when I added husky. So it is time to add it back i think.

[jcstein]

NOTE: the changes to blobstream-orchestrator/relayer should be made on the source of orchestrator-relayer repo, as well, as it is the "source" for these docs https://github.com/celestiaorg/docs/pull/1332/files#diff-71a7959e9b9aa32e7c4bf07cd396250ce69e30364ffe584c8188205ba03c01f4

UPDATE: done here in an open PR to orchestrator-relayer celestiaorg/orchestrator-relayer#661