Promote L2::Aruba to L3::Aruba

Aruba controllers can act as L3 devices and provide L3 information through the
standard MIBs.  This change makes Aruba devices get recognized as such.
Layer2.pm and Layer3.pm provide roughly the same functionality so there should
be little to no impact for Aruba devices only acting as L2 entities.

DeviceMatrix.txt

@@ -39,7 +39,7 @@ class: Layer3::Timetra
 device: All
 
 device-family: AOS
-class: Layer2::Aruba
+class: Layer3::Aruba
 device: All
 
 #
@@ -82,17 +82,19 @@ device: All
 # Aruba
 #
 device-vendor: Aruba
-arpnip: no
+arpnip: yes
 macsuck: yes
 portmac: yes
 duplex: no
-class: Layer2::Aruba
+class: Layer3::Aruba
 
 device-family: Aruba Wireless Controllers
 note: Uses proprietary MIBs to provide MAC to port mapping.  APs appear as switch ports.
 
 device: 5000
 
+device: 6000
+
 #
 # Asante
 #