Makes the Extension loader behavior predictable

When using a cluster of load-balanced Neutron Servers,
the order of extension files being loaded may differ
from one server to another. This is usually harmless,
but it is better to force the list to be loaded in the
same way across the entire cluster, just in case
something funky is going on.

Partial-bug: #1285999

Change-Id: Ib0bfd24fc52b6cd9f90c350d3af496f04a90f50a
Drop old nvp extension file

The resource alias is unchanged so there is really
no reason of dragging this forward.

If API clients are using the name or the description
in order to play with a server's extension they are
doing it wrong so they deserve the grief caused
by this change.

Change-Id: I99086c11a0e4a0b0af479e0e3d1fbe92f8ff5988
Closes-bug: #1285999
Floatingip_status migration not including Embrane's plugin

2eeaf963a447_floatingip_status migration script is not including Embrane's core plugin (thus breaking the tests).

Change-Id: Ic051ba2524db2e1bafea102af34351f6c4088db3
Closes-bug: 1289046
BigSwitch: Fix error for server config check

Raises config error when a port is incorrectly
configured for a server instead of getting a
ValueError when python tries to convert it to
an integer.

Closes-Bug: #1289132
Change-Id: Ifec0bec5640a4a57859f2673c46c610f1d21c36c
NSX: fix nonsensical log trace on update port

Having this at a WARN level makes no sense, especially
because the actually message does not say anything about
a warning condition. Probably a brain fart of some sort.
Make it DEBUG, just because it may come handy to see what
data we're passing.

Change-Id: Ie667018faae587a3adb6b3edda4d9912344cae83
Merge "Drop old nvp extension file"
Merge "NSX: fix nonsensical log trace on update port"
Merge "BigSwitch: Fix error for server config check"
Merge "Floatingip_status migration not including Embrane's plugin"
Merge "Makes the Extension loader behavior predictable"