No PF1 when compiled against DPDK 25.11.1

DPDK EAL argument for multiport-eswitch does not provide PF1 to the application anymore.

This command:

dpdk-testpmd -a 0000:03:00.0,class=rxq_cqe_comp_en=0,rx_vec_en=1,dv_flow_en=2,dv_esw_en=1,fdb_def_rule_en=2,representor=pf[0-1]vf[0-3]  -- --interactive

will show PF0+PF1+VFs on 25.11:

Configuring Port 0 (socket 0)
Port 0: 10:70:FD:F7:4B:A0
Configuring Port 1 (socket 0)
Port 1: 10:70:FD:F7:4B:A1
Configuring Port 2 (socket 0)
Port 2: 66:78:18:31:06:AA
Configuring Port 3 (socket 0)
Port 3: AE:5D:88:46:B4:29
Configuring Port 4 (socket 0)
Port 4: 72:C6:72:09:17:94
Configuring Port 5 (socket 0)
Port 5: 42:1B:EA:12:78:76
Checking link statuses...
Done

but on 25.11.1:

Configuring Port 0 (socket 0)
Port 0: 10:70:FD:F7:4B:A0
Configuring Port 1 (socket 0)
Port 1: 66:78:18:31:06:AA
Configuring Port 2 (socket 0)
Port 2: AE:5D:88:46:B4:29
Configuring Port 3 (socket 0)
Port 3: 72:C6:72:09:17:94
Configuring Port 4 (socket 0)
Port 4: 42:1B:EA:12:78:76
Checking link statuses...
Done

using git bisect, the breaking commit is this:
https://github.com/DPDK/dpdk-stable/commit/4e22d68ee129a9a8cdb46bd84c0de022dc93c1a8

however reverting such a big piece of code seems problematic

Start by reproducing the dpdk-testpmd command with DPDK 25.11 and 25.11.1, comparing the listed port output. Then inspect the breaking DPDK commit identified by git bisect (4e22d68ee129a9a8cdb46bd84c0de022dc93c1a). Done means PF1 and the expected PF/VF representors are available on 25.11.1 without reverting the entire change.