feat: revocation by document hash

[HJunyuan]

Context

• This reference implementation started off with revocation by document ID
• In order to align with how we perform revocation of documents issued onto the Ethereum document store, revocation by merkle root and intermediate hashes should be performed by the OCSP Responder (i.e. do not revoke by document id)

What does this PR do?

• Refactor naming convention from documentId -> documentHash
• Modify API response body: revoked = true / false, success = true / false, etc.
• Add plugins to support local development: npm run dev
• Improve readability of README
• Serverless deployment example: npm run deploy (i.e. sls deploy)

[cavacado]

clever, but reads poorly, could you wrap it around a generate range function and put it in utils?

[HJunyuan]

Certainly, will change it to:

Suggested change

	const REASON_CODES = [...Array(11).keys()];
	const REASON_CODES = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10];

[cavacado]

👍 lgtm lets go

[Abdulhakimsg]

Thanks for this feature! Extremely useful for our team

• In order to align with how we perform revocation of documents issued onto the Ethereum document store, revocation by merkle root and intermediate hashes should be performed by the OCSP Responder (i.e. do not revoke by document id)