Added a TriggerEvent when a job is created successfully, allowing developers to use an event listener and update ESX.Jobs, instead of importing the whole ESX object.

Description

Adds a TriggerEvent "esx:jobCreated" with job name (string) and job data (table), to allow allow developers to update/sync ESX.Jobs, using an event listener, without importing the ESX object.

Motivation

Allowing developers to easily update ESX.Jobs in their script with an event listener, instead of important the whole ESX object to sync the newly created job(s).

Implementation Details

The event has job name and job data as parameters, so instead of replacing the whole ESX.Jobs, you only add the relevant updates.

Usage Example

RegisterNetEvent("esx:jobCreated", function(jobName, jobData)
    if not jobName or type(jobName) ~= 'string' then
        return 
    end
    if not jobData or type(jobData) ~= 'table' then 
        return 
    end
    ESX.Jobs[jobName] = jobData
end)

PR Checklist

• My commit messages and PR title follow the Conventional Commits standard.
• My changes have been tested locally and function as expected.
• My PR does not introduce any breaking changes.
• I have provided a clear explanation of what my PR does, including the reasoning behind the changes and any relevant context.