Split call Function into Distinct Read and Execution Methods for Smart Contracts

[Ben-Rey]

Currently, the differentiation between reading and transactional operations within smart contracts is managed by the nonPersistentExecution parameter in the callSc method. This approach, while functional, can lead to confusion and obscures the intention behind contract interactions.
The call method should return a single data type, ensuring consistency across smart contracts and simplifying developer interaction.