feat: checking if the requested blueprint exists in the fullnode

[andreabadesso]

Motivation

We should validate the blueprint id before yielding prompts to the clients

Acceptance Criteria

• We should request the fullnode for the blueprint information and fail if unable to fetch it.

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged
• Make sure either the unit tests and/or the QA tests are capable of testing the new features
• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[pedroferreira1]

Suggested change

	export class BluePrintNotFoundError extends ParamsValidationError {};
	export class BlueprintNotFoundError extends ParamsValidationError {};

[pedroferreira1]

We should also check that the nc_id (if not executing a initialize method) is a valid nano_contract_id

[alexruzenhack]

todo: I believe it is lacking a validation on the methods existence after confirming that the blueprint exists.

[alexruzenhack]

It is lacking a validation. See this comment #16 (comment)