add new `invalid` job status

[rafaelcr]

To distinguish between jobs that failed because of an unhandled exception or something else that did go wrong (failed) vs jobs that failed because the thing to be processed (token or contract) is invalid or not compatible with SIP-016 metadata standards.

We should also make sure to respond with "invalid token" or something similar when the user requests token metadata for one of these invalid tokens/contracts

[rafaelcr]

Example wrapped token contracts that have incorrect metadata (as far as SIP-010 is concerned):

• SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wxusd
• SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wslm
• SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wusda
• SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wdiko
• SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wban
• SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-wmia

;; @desc get-total-supply
;; @returns (response uint)
(define-read-only (get-total-supply)
  ;; least authority Issue D
  ERR-NOT-SUPPORTED
)

[blockstack-devops]

🎉 This issue has been resolved in version 0.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀