Create generic end action to more easily create custom actions #1306
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Current behavior
Creating a new component with body and then as a closing
{{end elem="mycustomelement" }} element require to add code in the core of yeswiki to add **customelement** intoend.php` file.Expected behavior
I would like to be ablo to add a custom element without modifying something that could be removed by update.
Proposal
We could had a default case for end element that look for a
end()fonction in the extra YesWiki action like this :