fix(services/scaffolder): add no-message parameter for checkComponentCreated method

[Pantani]

closes #1379

What does this MR does?

scaffold map foo fails when CreateFoo message exists, this PR add noMessage condition to avoid false check

How to test?

• Create a list

$ starport scaffold chain github.com/cosmonaut/scavenge --no-module
$ cd scavenge
$ starport scaffold module scavenge --dep bank
$ starport scaffold message create-scavenge solutionHash description reward

# Try to scaffold a type with a message, it must fail
$ starport scaffold map scavenge solutionHash solution description reward scavenger

# Try to scaffold a type without a message, it must succeed
$ starport scaffold map scavenge solutionHash solution description reward scavenger --no-message

[Pantani]

This PR solves the issue, but I think we should refactor the check method. We are doing an unnecessary check for some scaffold types

[lumtis]

I think this is a good workaround for the specific issue of the tutorial

In the future we would actually need to refactor checkComponentCreated by fetching the type names for the specific component to scaffold and check if one of them exist in the package