feat: added complex types and types in restriction component of smart contract (#361)

Author: RutvikGhaskataEalf

docs/learn/smart-contract/requirements-and-restrictions/namespace-and-type-restrictions/index.md

@@ -64,6 +64,15 @@ When deploying new contract code, Nodes perform checks against a whitelist. If a
 | string                        | ALL                     | Allowed   |
 | string                        | Constructor             | Denied    |
 | Byte[]                        | ALL                     | Allowed   |
+| Func 4                        | ALL                     | Allowed   |
+| ValueTuple 1                  | ALL                     | Allowed   |
+| ValueTuple 2                  | ALL                     | Allowed   |
+| ValueTuple 3                  | ALL                     | Allowed   |
+| ValueTuple 4                  | ALL                     | Allowed   |
+| ValueTuple 5                  | ALL                     | Allowed   |
+| ValueTuple 6                  | ALL                     | Allowed   |
+| ValueTuple 7                  | ALL                     | Allowed   |
+| ValueTuple 8                  | ALL                     | Allowed   |
 
 ## Types and Members Whitelist in System.Reflection Namespace
 

docs/learn/smart-contract/requirements-and-restrictions/structure-restrictions-and-requirements/index.md

@@ -183,4 +183,5 @@ In contract state, only the following types are allowed:
 - `MappedState<T, T, T, T, T>`
 - `MethodReference<T, T>`
 - `ProtobufState<T>`
-- `ContractReferenceState`
+- `ContractReferenceState`
+- `StructuredState`