fix: handle redacted items on project

[dsanders11]

Issues transferred to private repos will show up on the project as redacted items, which have no content available. Properly handle this case.

Copilot reviewed 21 out of 26 changed files in this pull request and generated no comments.

Files not reviewed (5)

• tests/delete-project.test.mts: Evaluated as low risk
• tests/get-item.test.mts: Evaluated as low risk
• src/get-item.ts: Evaluated as low risk
• src/edit-item.ts: Evaluated as low risk
• tests/copy-project.test.mts: Evaluated as low risk

Comments suppressed due to low confidence (3)

tests/lib.test.ts:450

• The assertion should check the exact arguments passed to execCliCommand for stronger validation.

expect(execCliCommand).toHaveBeenCalledWith(expect.arrayContaining([owner, projectNumber]));

tests/lib.test.ts:1046

• Ensure that the tests cover the new structure properly, especially since the __typename property has been removed.

const { content, type } = items[0];

tests/edit-item.test.mts:170

• [nitpick] The error message 'Cannot edit redacted items' could be more descriptive. Consider changing it to 'Cannot edit items that have been redacted due to privacy or security reasons'.

Cannot edit redacted items