[bug]: Time condition loop

[jimwinme]

FreePBX Version

FreePBX 15

Issue Description

I'm calling this a bug, because the setting obviously shouldn't be allowed by the module. A user inadvertently modified a time condition to point to itself under "Destination non-matches" and Freepbx accepted it. This basically shut down the inbound route that pointed to the condition. It seems like it could be a minor fix, as basically the select options would just need to not include the currently edited time condition as is already the case for the "matches" field.

Operating Environment

FreePBX 15.0.37.4 and also tested on a FreePBX 16.0.40.7 system that is in pre-deployment testing with same result.

Relevant log output

N/A