Improve performance on Tower schedule runs with bugfix for missing schedules

[paulbarfuss]

What does this PR do?

• Fix a condition in latest process-project update where is true fails and should be == true
• Use the 400 response code when creating a schedule with a POST to determine if it should instead be updated with a PUT
• Use /api/v2/schedules/?name={{ schedule.name }} to lookup existing schedules instead of looping through all schedules. This will enhance performance while bypassing a potential bug where not all schedules show up in the global /api/v2/schedules even when accounting for pagination. (The API browser is also missing some schedules from the global endpoint)

How should this be tested?

Tested all changes against one of the failing playbooks in Tower by pointing to the incoming paulbarfuss/infra-ansible fork/branch.

For some unknown reason, when looking up all schedules in {{ ansible_tower_url }}/api/v2/schedules/ using the rest_get module a few are not appearing. For example:

• {{ ansible_tower_url }}/api/v2/schedules/86 does not appear in the global schedules
• {{ ansible_tower_url }}/api/v2/job_templates/94/schedules/ does include the schedule with "id": 86
• {{ ansible_tower_url }}/api/v2/schedules/?name={{ schedule.name }} quickly finds the correct schedule.id and only checks once we know from the 400 response code that the schedule does indeed already exist.

People to notify

cc: @redhat-cop/infra-ansible