text: Title: RFE: Implement Maximum Execution Limit for Scheduled Successful Jobs
  Body: ### Please confirm the following
  
  - [X] I agree to follow this project's [code of conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
  - [X] I have checked the [current issues](https://github.com/ansible/awx/issues) for duplicates.
  - [X] I understand that AWX is open source software provided for free and that I might not receive a timely response.
  
  ### Feature type
  
  New Feature
  
  ### Feature Summary
  
  **Context:**
  The current version of AWX allows users to schedule job executions, but it does not offer a way to automatically disable these schedules after a certain number of successful executions. This enhancement proposes adding a feature to limit the maximum number of executions for a schedule. For example, a user could set a schedule to run a job three times every day, but after a total of nine successful executions, the schedule should automatically disable itself. This feature would be particularly useful in managing resources and ensuring that tasks do not run indefinitely.
  
  Consider a scenario where schedules are dynamically generated to perform specific checks a few times a day over several days. After the desired number of checks, it would be beneficial for the schedule to deactivate automatically.
  
  Schedules in AWX function similarly to a distributed cron job. By implementing this feature, it would be akin to having a distributed version of the "at" command, enhancing the flexibility and control over task executions in AWX.
  
  **Use Case:**
  This feature would be beneficial in scenarios where a task is required to run only a limited number of times, such as:
  
    - Temporary projects or jobs that are only relevant for a certain period or a specific number of executions.
    - Compliance or policy requirements that mandate certain tasks not exceed a specified number of runs.
    - Testing environments where jobs are needed for a finite number of runs to validate behavior under controlled repetitions.
  
  **Impact:**
    - Positive: Enhances control over job execution, prevents resource wastage, and improves manageability.
    - Negative: Slight increase in the complexity of the scheduling interface and additional validation required to manage the execution count.
  
  ### Select the relevant components
  
  - [X] UI
  - [X] API
  - [X] Docs
  - [X] Collection
  - [X] CLI
  - [ ] Other
  
  ### Steps to reproduce
  
  RFE
  
  ### Current results
  
  RFE
  
  ### Sugested feature result
  
  RFE
  
  ### Additional information
  
  _No response_