feat: fetching retrieves non-revoked keys for a payment pointer

[JoblersTune]

Changes proposed in this pull request

• When fetching payment pointer keys only non-revoked keys are returned

Context

• fixes Do not return revoked keys when fetching payment pointer keys #1760

Checklist

• Related issues linked using fixes #number
• Tests added/updated
• Documentation added
• Make sure that all checks pass
• Postman collection updated

[netlify]

✅ Deploy Preview for brilliant-pasca-3e80ec canceled.

Name	Link
🔨 Latest commit	66a6cef
🔍 Latest deploy log	https://app.netlify.com/sites/brilliant-pasca-3e80ec/deploys/64f84a3884a476000860599b

[JoblersTune]

I have updated the getKeysByPaymentPointerId service function. I wasn't sure if I needed to include any filtering in the routes file where keys are returned based on deps.config.paymentPointerUrl === ctx.paymentPointerUrl

  deps: ServiceDependencies,
  ctx: PaymentPointerKeysContext
): Promise<void> {
  if (ctx.paymentPointer) {
    const keys = await deps.paymentPointerKeyService.getKeysByPaymentPointerId(
      ctx.paymentPointer.id
    )

    ctx.body = {
      keys: keys.map((key) => key.jwk)
    }
  } else if (deps.config.paymentPointerUrl === ctx.paymentPointerUrl) {
    ctx.body = {
      keys: [deps.jwk]
    }
  } else {
    return ctx.throw(404)
  }
}``` 

[mkurapov]

@JoblersTune good q, I would say we don't add any filters here because this is the key that is "issued" for the Rafiki instance itself (used when making inter-Rafiki requests, for example to get grants from another Rafiki instance). The key shouldn't be revoked, or some things might break.