Not a reasonable duration of 1M prefix introduction from BGP application peer via restconf

Not a reasonable period (not comparable to 1M BGP peer scenario) needed for 1M prefixes introduction from BGP application peer (restconf) to controller and to BGP peer (BGP Updates). It points to performance issue and/or lack of environment specification and expected result definition for such case.

bgpcep-bgp-ingest.txt.Bgp App Peer Prefixcount :: BGP performance of ingest...
==============================================================================
Check_For_Empty_Ipv4_Topology_Before_Starting :: Wait for example-... | PASS |
------------------------------------------------------------------------------
Reconfigure_ODL_To_Accept_Connection :: Configure BGP peer module ... | PASS |
------------------------------------------------------------------------------
Reconfigure_ODL_To_Accept_BGP_Application_Peer :: Configure BGP ap... | PASS |
------------------------------------------------------------------------------
Connect_BGP_Peer :: Start BGP peer tool | PASS |
------------------------------------------------------------------------------
Start_BGP_Application_Peer_To_Introduce_Routes :: Start BGP applic... | PASS |
------------------------------------------------------------------------------
Wait_For_Ipv4_Topology_Is_Filled :: Wait until example-ipv4-topolo... | FAIL |
Keyword 'PrefixCounting.Check_Ipv4_Topology_Count' failed after retrying for 5 minutes 20 seconds. The last error was: 32358 != 1000000

test suite: https://git.opendaylight.org/gerrit/#/c/30256/15
test log temporary available at https://jenkins.opendaylight.org/sandbox/job/bgpcep-csit-1node-periodic-bgp-ingest-only-stable-lithium/26/console

Note: test suite follows specifications: https://wiki.opendaylight.org/view/BGP_LS_PCEP:Programmer_Guide#BGP
https://wiki.opendaylight.org/view/BGP_LS_PCEP:User_Guide#BGP_Application_Peer