netplan device order does matter (has been fixed in past)

[Marcus Wellnitz]

defining a bridge device _before_ the ethernet devices triggers an error:

`netplan apply`failes if you specify a virtual devices before their member devices.

Was fixed in the past according to this bug report: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1670495

Problem: When deploying via ansible the order is mixed up. In my case 'bonds' are always before 'ethernets' and netplan fails

affects:
* 18.04 LTS (Bionic Beaver)
* netplan.io 0.36.3
* netplan.io 0.36.1

[Lukas Märdian (slyon)]

I cannot reproduce this on a recent release of netplan (using Ubuntu Jammy) nor on Bionic. Using this configuration, the bridge is created correctly:

network:
    version: 2
    bridges:
      br0:
        interfaces: [eth0]
    ethernets:
        eth0:
            dhcp4: true

Please re-open if this is still an issue.