mlx4_core: use higher log_rdmarc_per_qp when scale_profile is set

mlx4_core: use higher log_rdmarc_per_qp when scale_profile is set

Another parameter log_rdmarc_per_qp is scaled up to higher
value (128) when scale_profile is set based on new requirement.

The commit
58f318ea1272 "net/mlx4_core: Modify default value of
              log_rdmarc_per_qp to be consistent with HW capability"
was modifying the Mellanox defaults to accomplish the same but
this change uses scale_profile to be consistent with all the
other changes from Mellanox defaults done for HCA parameters.

This also (indirectly) fixes a code merge issue
with  following commits where a change to default value
of log_rdmarc_per_qp got inadvertently reverted as
two independent changes that interacted were done
in the same merge window (albeit this fix does it with a
slightly different implementation):

58f318ea1272 "net/mlx4_core: Modify default value of
              log_rdmarc_per_qp to be consistent with HW capability"
3480399bdf6d "mlx4_core: scale_profile should work without params
              set to 0"

Orabug: 23725942

Signed-off-by: Mukesh Kacker <mukesh.kacker@oracle.com>
Reviewed-by: Yuval Shaia <yuval.shaia@oracle.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>