feat!: add LSP11 package

[YamenMerhi]

What does this PR introduce?

🚀 Feature

• Adding LSP11

PR Checklist

• Wrote Tests
• Wrote & Generated Documentation (readme/natspec/dodoc)
• Ran npm run lint && npm run lint:solidity (solhint)
• Ran npm run format (prettier)
• Ran npm run build
• Ran npm run test

[CJ42]

Added first round of review.

You also need to register the package in the release-please-config.json file.

lsp-smart-contracts/release-please-config.json

Lines 176 to 202 in f4def52

	},
	"packages/lsp17contractextension-contracts": {
	"component": "lsp17contractextension-contracts",
	"package-name": "@lukso/lsp17contractextension-contracts",
	"include-component-in-tag": true,
	"release-type": "node",
	"bump-minor-pre-major": true,
	"bump-patch-for-minor-pre-major": false,
	"draft": false,
	"prerelease-type": "rc",
	"extra-files": [
	"packages/lsp17contractextension-contracts/contracts/Version.sol"
	]
	},
	"packages/lsp23-contracts": {
	"component": "lsp23-contracts",
	"package-name": "@lukso/lsp23-contracts",
	"include-component-in-tag": true,
	"release-type": "node",
	"bump-minor-pre-major": true,
	"bump-patch-for-minor-pre-major": false,
	"draft": false,
	"prerelease-type": "rc"
	}
	},
	"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
	}

[CJ42]

added 2nd round of review for the Solidity code

[CJ42]

Here since there are so many, the specific import syntax would be quite big, so maybe we could do:

Suggested change

	import "./LSP11Errors.sol";
	import ./LSP11Errors.sol" as Errors;

And then reference like that:

revert Errors.NotAGuardian(...)

wdyt?

[YamenMerhi]

I don't see the value in adding it

[CJ42]

would it make sense to show that as public for block explorers?

[CJ42]

encode or encode packed?

[YamenMerhi]

No preference