Applied ABC work-around to avoid LUT mapping fail.

[openroad-ci]

• It can avoid the ABC issue in a hierarchical flow: Mapping into LUTs has failed berkeley-abc/abc#432

[jhkim-pii]

• Alan Mishchenko provided the work-around.
• No QoR impact in flat flow: https://dashboard.precisioninno.com/compare?sourceAType=Commit&sourceBType=Commit&designs=aes%2Cariane133%2Cariane136%2Cbp%2Cbp_be%2Cbp_fe%2Cbp_multi%2Cdynamic_node%2Cgcd%2Cibex%2Cjpeg%2Cmempool_group%2Cswerv%2Cswerv_wrapper%2CtinyRocket&sourceAName=c8bdbc9a977b6e84d36f0b1d88729056ba415c86&sourceAID=2&sourceBName=3dc3b3b47cb7bac8c2b08691c9e4b1f84862f6a4&sourceBID=1
• But hierarchical flow QoR is affected by the W/A: https://dashboard.precisioninno.com/compare?designs=aes%2Caes_lvt%2Caes-block%2Caes-mbff%2Ccva6%2Cethmac%2Cethmac_lvt%2Cgcd%2Cgcd-ccs%2Cibex%2Cjpeg%2Cjpeg_lvt%2Cmock-alu%2Cmock-array%2Cmock-cpu%2Criscv32i%2Criscv32i-mock-sram%2Cswerv_wrapper%2Cuart&sourceAType=Commit&sourceBType=Commit&sourceAName=fadd43bc568f73c1162e39470baaa8f6e542403f&sourceAID=7&sourceBName=755b0ce717231d5b16d68617214729125bf35331&sourceBID=8

@precisionmoon @povik @maliberty Can we apply the work-around in ORFS?
I think hierarchical flow QoR is not important at this stage (Functional bug fixing. Not started QoR analysis yet).

[povik]

I've looked up the meaning of -r:

	-r     : toggle skipping choices with redundant support [default = no]

I see no issue with the workaround.