feat: typos, removed unsafeBurn, modify unsafeMint

[jatZama]

No description provided.

[PacificYield]

Just one comment about the packageManager

[jatZama]

All tests are working now, so this PR is ready to be merged after review. VERY Important: After my new implementation of Error handling, I noticed one of your test "should be able to transferFrom only if allowance is sufficient" inside EncryptedERC20WithError.test.ts had two logical errors that I fixed. Could you double check that now the correct test logic is indeed implemented please before merging? @PacificYield thanks.
I will let you add later on top of this PR the other features you added, like the new error names etc, after we merge this big PR.

[PacificYield]

uint256 errorId = _errorCounter++;
You can increment on the same lane.

[jatZama]

this reduces readability and doesn't save gas, i dont think it is a good idea

[PacificYield]

OK!

[PacificYield]

LGTM.

A few suggestions:

• Start all functions/variables that are internal with underscore (_) https://docs.soliditylang.org/en/latest/style-guide.html#underscore-prefix-for-non-external-functions-and-variables
• For all functions that deal with errors (from EncryptedErrors), I suggest to start with a recognizable prefix such as "_errorDefineIf", "_errorDefineIfNot". It would help standardizing encrypted error management for future use cases and make it very apparent for developers. --> Can be done in later stages.
• Make sure to follow the Solidity pattern for visibility of functions or at least be consistent (external / public /internal /private)

[PacificYield]

All tests are working now, so this PR is ready to be merged after review. VERY Important: After my new implementation of Error handling, I noticed one of your test "should be able to transferFrom only if allowance is sufficient" inside EncryptedERC20WithError.test.ts had two logical errors that I fixed. Could you double check that now the correct test logic is indeed implemented please before merging? @PacificYield thanks. I will let you add later on top of this PR the other features you added, like the new error names etc, after we merge this big PR.

I prefer we merge this one and I'll rebase the other PR and continue on this one!

[jatZama]

All tests are working now, so this PR is ready to be merged after review. VERY Important: After my new implementation of Error handling, I noticed one of your test "should be able to transferFrom only if allowance is sufficient" inside EncryptedERC20WithError.test.ts had two logical errors that I fixed. Could you double check that now the correct test logic is indeed implemented please before merging? @PacificYield thanks. I will let you add later on top of this PR the other features you added, like the new error names etc, after we merge this big PR.

I prefer we merge this one and I'll rebase the other PR and continue on this one!

I agree, this is what I wanted to do exactly.

[jatZama]

• Make sure to follow the Solidity pattern for visibility of functions or at least be consistent (external / public /internal /private)

I am not sure to understand what do you mean here? I noticed several points here:
1/ I dunno why you converted all the variables from private to internal. In OZ , almost all variables are private fyi.
2/ Imo the layout and order of functions that you chosed is not very clear. I prefer to use in general this kind of layout to roder functions by their visibility: https://github.com/Cadmos-finance/Stake2Care-sc/blob/master/src/ImpactVault.sol