No warnings for high route utilization when running CRM tests

[daall]

Description
The IPv4/IPv6 route CRM tests are failing against the master image because no THRESHOLD EXCEEDED message is ever received.

Steps to reproduce the issue:

1. Run crm_route test.

Describe the results you received:

# Verify thresholds for "IPv[4/6] route" CRM resource
        verify_thresholds(duthost, crm_cli_res="ipv{ip_ver} route".format(ip_ver=ip_ver),
>           crm_used=new_crm_stats_route_used, crm_avail=new_crm_stats_route_available)

>           raise LogAnalyzerError(result)
E           LogAnalyzerError: {'match_messages': {'/tmp/syslog.2020-10-06-08:49:54': []}, 'total': {'expected_match': 0, 'expected_missing_match': 1, 'match': 0}, 'match_files': {'/tmp/syslog.2020-10-06-08:49:54': {'expected_match': 0, 'match': 0}}, 'expect_messages': {'/tmp/syslog.2020-10-06-08:49:54': []}, 'unused_expected_regexp': ['.* THRESHOLD_EXCEEDED .*']}

Describe the results you expected:
Threshold should be hit, tests should pass.

Output of show version:

admin@str2-dx010-acs-6:~$ show ver

SONiC Software Version: SONiC.master.432-dbea3bbf
Distribution: Debian 10.6
Kernel: 4.19.0-9-2-amd64
Build commit: dbea3bbf
Build date: Sun Oct  4 07:55:05 UTC 2020
Built by: johnar@jenkins-worker-8

Platform: x86_64-cel_seastone-r0
HwSKU: Celestica-DX010-C32
ASIC: broadcom
Serial Number: DX010F2B118711MS100005
Uptime: 00:06:31 up  9:46,  1 user,  load average: 1.48, 1.88, 1.94

Docker images:
REPOSITORY                    TAG                   IMAGE ID            SIZE
docker-teamd                  latest                74965f9b1b74        394MB
docker-teamd                  master.432-dbea3bbf   74965f9b1b74        394MB
docker-sonic-mgmt-framework   latest                089d9821089a        486MB
docker-sonic-mgmt-framework   master.432-dbea3bbf   089d9821089a        486MB
docker-router-advertiser      latest                ccf4c000ca77        359MB
docker-router-advertiser      master.432-dbea3bbf   ccf4c000ca77        359MB
docker-platform-monitor       latest                7fa84a15fa6a        441MB
docker-platform-monitor       master.432-dbea3bbf   7fa84a15fa6a        441MB
docker-lldp                   latest                0f2bfd338de9        388MB
docker-lldp                   master.432-dbea3bbf   0f2bfd338de9        388MB
docker-dhcp-relay             latest                330f61e7cfd4        366MB
docker-dhcp-relay             master.432-dbea3bbf   330f61e7cfd4        366MB
docker-database               latest                ddf2b1a6d1f9        359MB
docker-database               master.432-dbea3bbf   ddf2b1a6d1f9        359MB
docker-orchagent              latest                d7e20f12b519        407MB
docker-orchagent              master.432-dbea3bbf   d7e20f12b519        407MB
docker-nat                    latest                150fdbf00d3b        396MB
docker-nat                    master.432-dbea3bbf   150fdbf00d3b        396MB
docker-sonic-telemetry        latest                8bb6c262235f        429MB
docker-sonic-telemetry        master.432-dbea3bbf   8bb6c262235f        429MB
docker-fpm-frr                latest                10c1e544461b        410MB
docker-fpm-frr                master.432-dbea3bbf   10c1e544461b        410MB
docker-sflow                  latest                52d1523a3a21        397MB
docker-sflow                  master.432-dbea3bbf   52d1523a3a21        397MB
docker-snmp                   latest                60da1622f89e        399MB
docker-snmp                   master.432-dbea3bbf   60da1622f89e        399MB
docker-syncd-brcm             latest                f72787223d2e        447MB
docker-syncd-brcm             master.432-dbea3bbf   f72787223d2e        447MB

[daall]

This is most likely related to #5570