Add documentation to ExecuteCommand native

[NotLazy]

Goal of this PR

The goal of this PR is to help anyone else that experiences the same issue I did, with being unable to use ExecuteCommand in my resource, without first adding an acl for the resource, and attempting to google the issue only told me how to add ACLs for players.

How is this PR achieving the goal

This PR is achieving that goal by adding documentation to the ExecuteCommand native, to include a simple pointer towards how to add an acl for a resource.

This PR applies to the following area(s)

Natives

Successfully tested on

Game builds: N/A

Platforms: N/A

Checklist

• Code compiles and has been tested successfully. (N/A)
• Code explains itself well and/or is documented. (N/A)
• My commit message explains what the changes do and what they are for.
• No extra compilation warnings are added by these changes.

Fixes issues

N/A

[Yum1x]

I checked the Register Command docs and they already cover that stuff. I think your PR might just be an oversight

[NotLazy]

I checked the Register Command docs and they already cover that stuff. I think your PR might just be an oversight

I disagree. Register Command does not mention ACLs for resources specifically. It only mentions players, and doesn't mention how to do it. It mentions that ExecuteCommand can be used to execute registered commands but again does not mention ACLs for resources.

If anything, what would be better than this PR would be having resources mentioned in the add_ace example section

[prikolium-cfx]

Thanks for the contribution