text: Title: Possibility to continue execution after WHILE limit is reached
  Body: Hello everyone,
  
  I'm creating this issue to discuss about a potential evolution of the WHILE loop behaviour when the limit is reached. As a reminder, in the current implementation of the WHILE loop, when the limit is reached, execution fails with the following message `WHILE loop was aborted because it did not finish within the limit of 5 iterations. Use the 'limit' argument to increase or remove the limit if needed.` (if the limit is 5 iterations).
  
  In this PR #4561, I suggested to add a third argument in order to be able to set a custom error message when the limit is reached. @pekkaklarck suggested to use this third argument to control what to do if the limit is reached and, for example, allow execution to continue even if the limit is reached.
  
  I have been thinking about it and as a result, I imagined the following scenarios :
  
  
  ```
  *** Test Cases ***
  Continue after limit is reached
      [Documentation]  The execution will continue after the WHILE loop even if the limit is reached
      WHILE    True    limit=5    limit_reached_behavior=CONTINUE
          Log     Test
      END
  
  Fail with custom error message if limit is reached
      [Documentation]  The execution will fail with custom error message if the limit is reached
      WHILE    True    limit=5    limit_reached_behavior=Fail    Custom error message
          Log     Test
      END
  
  Run keyword and continue if limit is reached
      [Documentation]  The execution will execute the keyword and continue execution if the limit is reached
      WHILE    True    limit=5    limit_reached_behavior=Example keyword
          Log     Test
      END
  
  *** Keywords ***
  Example keyword
      Log     Example
  ```
  
  If `limit_reached_behavior` equals `CONTINUE`, the execution simply continues if the limit is reached. 
  If `limit_reached_behavior` doesn't equal `CONTINUE`, the keyword given in `limit_reached_behavior` is executed.
  
  What do you think of such scenarios ? Feel free to suggest other scenarios !
  
  I am not very comfortable with the idea of using `CONTINUE` to continue execution if the limit is reached because the string `CONTINUE` is already used to stop executing the current loop iteration and continues to the next one.
  
  It would also be very interesting to discuss what the option name should be.
  
  Such scenarios also beg the following question : Where and How should we display the keyword executed after reaching the limit in `log.html` ?
  
  Thank you very much for taking the time to read this issue !