Not found SKUs message logic added

[GabrielBarross]

What is the purpose of this pull request?

Based on the last affiliates-commission-service PR, we are adding two new graphQL operations to be used by the front end.
When a client uploads a new commissions spreadsheet, the back end will return if some of the IDs were not found by our catalog API, and by clicking on verifying the SKUs the client will be able to know if some error happened

What problem is this solving?

Better user experience

How to test it?

Accessing the link below and uploading some spreadsheets
https://commissionstest--bibiafiliados.myvtex.com/admin/affiliates-commissions

Screenshots or example usage

How does this PR make you feel? 🔗

Types of changes

• Chore (non-breaking change which doesn't change any functionalities)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires change to documentation, which has been updated accordingly.

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[github-actions]

Fails

🚫

We follow keepachangelog standards. Please, change the file CHANGELOG.md adding a small summary of your changes under the [Unreleased] section. Example: ## [Unreleased] + ### Fixed + - Issue with image sizing in the SKU Selector. Possible types of changes: Added for new features. Changed for changes in existing functionality. Deprecated for soon-to-be removed features. Removed for now removed features. Fixed for any bug fixes. Security in case of vulnerabilities.

Generated by 🚫 dangerJS against d358d5b

[wagnerlduarte]

Use prevent return in this case I think it's a better idea.

Suggested change

	return (
	<>
	{notFound === true ? (
	<Alert variant="warning">
	{intl.formatMessage(messages.affiliateCommissionWarning)}
	</Alert>
	) : (
	<Alert variant="positive">
	{intl.formatMessage(messages.affiliateCommissionSuccess)}
	</Alert>
	)}
	</>
	)
	if (notFound) {
	return (
	<Alert variant="warning">
	{intl.formatMessage(messages.affiliateCommissionWarning)}
	</Alert>
	)
	}
	return (
	<Alert variant="positive">
	{intl.formatMessage(messages.affiliateCommissionSuccess)}
	</Alert>
	)

[wagnerlduarte]

Suggested change

	{dataSKUs?.getNotFoundCommissions !== undefined ? (
	<CommissionsNotFound notFound={dataSKUs.getNotFoundCommissions} />
	) : null}
	{dataSKUs?.getNotFoundCommissions && <CommissionsNotFound notFound={dataSKUs.getNotFoundCommissions} />}