feature suggestion: add a notation for callbacks that expects the user to implement

There exist some callbacks in the LÖVE framework, like love.conf, love.draw and some others, and there is currently no way in EmmyLua to note that they are callbacks rather than normal functions, and that a new definition of the same function is an implementation rather than a new overload.

Current Behavior

No way to indicate that this is a callback instead of a normal function definition.

-- In the API definition.
---xxx
---@param t string
function callback(t) end


-- In user code
function callback(t)
    t:$
end

There is no completion based on the type of the parameter or ...

Suggested Behavior

Add a new notation for callbacks so when user is defining a new implementation, they can get completion on the parameters. This is especially useful when the parameter is extremely complex (for an example, see love.conf)

-- In the API definition.
---@callback
---xxx
---@param t string
callback = nil

-- In the user code
function callback(t)
    t:$
end

I am totally open to the specific syntax, and I think what is really important is to have a syntax for them.

Commencez par retracer la manière dont les EmmyLua annotations et les définitions de fonctions sont représentées, puis comparez cela avec les callbacks de LÖVE nommés dans l’issue. Décidez de la syntaxe des callbacks et de son interaction avec les implémentations utilisateur et la complétion des paramètres. C’est terminé lorsque la notation distingue les callbacks des fonctions ordinaires et permet la complétion des paramètres des callbacks ; aucun fichier ni test n’est nommé.