Add StartupArguments to starting resources

[CrosRoad95]

Is your feature request related to a problem? Please describe.

Add option to provide startup arguments for resources, client and server side.
It is very common pattern to send configuration, ccache of certain things to client when resource start, example: https://github.com/Patrick2562/mtasa-pAttach/blob/master/src/server.lua#L21

Describe the solution you'd like

startResource(getResourceFromName("foo"), ..., { foo = "foo", bar = 123 })

then in "foo" resource in resource start event you can read those arguments:
And option to set startup arguments for client only in "onResourceStart" event.

addEventHandler ( "onResourceStart", root, function(resource, arguments)
  if(resource == getThisResource())then
    setClientStartupArguments({ foo = "foo"}) -- ok
    setClientStartupArguments({ foo = "foo"}) -- argument already set, throw error
  else
    setClientStartupArguments({ foo = "foo"}) -- not okey because other resource is starting, throw error
  end
end)

setClientStartupArguments({ foo = "foo"}) -- can not use outside onResourceStart event

clientside:

addEventHandler ( "onClientResourceStart", root, function(resource, arguments)
     if(resource == getThisResource())then
      outputChatBox(arguments.foo) -- prints "foo"
    else
      print(arguments) -- always nil
    end
end)

serverside:

addEventHandler ( "onResourceStart", root, function(resource, arguments)
     if(resource == getThisResource())then
      outputChatBox(arguments.foo) -- prints "foo"
    else
      print(arguments) -- always nil
    end
end)

Possibly arguments should be only available in resource that own given resource, so i can not read startup arguments of other resources.
Also, another good use case would be mysql resource. Mta could support option to provide startup arguments from mtasercer.conf:

<resource src-"mysql" startup"1" protected="1">
  <startupArgument name="login" value="..." />
  <startupArgument name="password" value="..." />
</resource>

Describe alternatives you've considered

No response

Additional context

Would be very handy in slipe-server :)

Security Policy

• I have read and understood the Security Policy and this issue is not about a cheat or security vulnerability.