Fix wrong cluster configuration used when multiple match

When using lanpower on abacus25-2, lanpower took the first matching cluster configuration. So if we have both abacus2 and abacus25 in the configuration, lanpower just took the first declared.

This commit change that: now when using lanpower on abacus25-2, lanpower now look for an exact match of abacus25 in the configuration.