feat: fix the manifest wording in the repo

[nikita-quantstamp]

We have some leftover wording from the old manifest setup in the code, so I removed that from the comment, as validation functions are no longer part of the manifest.

I was going to update the wording in the standard itself from manifest to execution manifest, as that more accurately reflects the current state of the manifest, but we use it interchangeably through the ERC, so I'm not too sure there. Should we commit to one of them? What do people think?

[octane-security-app]

Summary by Octane

New Contracts

No new contracts were added in this PR.

Updated Contracts

• IModularAccount.sol: Removed validation against the manifest for installing validation functions.

---

🔗 Commit Hash: a2ada19

[octane-security-app]

Overview

Octane AI analysis has finished. No vulnerabilities were found. Cheers! 🎉🎉🎉

---

🔗 Commit Hash: a2ada19

[jaypaik]

I was going to update the wording in the standard itself from manifest to execution manifest, as that more accurately reflects the current state of the manifest, but we use it interchangeably through the ERC, so I'm not too sure there. Should we commit to one of them? What do people think?

I think maybe in the installation/uninstallation section we can change "module manifest" to "module's manifest" or "module's execution manifest". But otherwise seems fine to leave other things be, and have it be implied that "manifest" refers to ExecutionManifest.

[jaypaik]

Happy to just keep the manifest wording as is. And with #210, we'll be removing the standard from the reference implementation, so we don't have to make that change here.