docs: add documentation for revoking and activating a VC

[huynguyen-hl]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Description

This PR adds guidance on how to revoke and activate a VC using APIs.

Related Tickets & Documents

https://github.com/gs-gs/fa-ag-trace/issues/595

Mobile & Desktop Screenshots/Recordings

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 vc-kit doc site
• 📕 storybook
• 🙅 no documentation needed

[github-actions]

Coverage report

Caution

Coverage does not meet threshold
Statements coverage not met for global: expected <=25 not covered statements, but got 0

St.❔	Category	Percentage	Covered / Total
🟢	Statements	100%	0/0
🟢	Branches	100%	0/0
🟢	Functions	100%	0/0
🟢	Lines	100%	0/0

Test suite run success

0 tests passing in 0 suite.

Report generated by 🧪jest coverage report action from afdb319

[ashleythedeveloper]

This LGTM, can someone confirm the payloads/responses?

[namhoang1604]

Should we introduce the issuing bitstring status flow?

[huynguyen-hl]

@namhoang1604, Yes, I agree with you about adding the issuing BitstringStatusList flow to the documentation site. However, since there are currently no flow charts in the entire site, I believe we need a ticket to create flow charts for all the APIs that already have documentation. If we only include the flow chart for the issuing BitstringStatusList, it might make the documentation site a bit inconsistent, don’t you think?

[namhoang1604]

LGTM