wscript: use consistent python shebang path

Most wscripts use
  #!/usr/bin/env python
Use that consistently.

The wscripts are not executed directly and do not need the shebang path,
but it might guide editors and other tools to recognize the files as
being Python-ish.

share/export/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/mcp/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/media/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/midi_maps/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/osc/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/patchfiles/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/plugin_metadata/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

share/scripts/wscript

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 
 import os
 

tools/bb/wscript

@@ -1,3 +1,4 @@
+#!/usr/bin/env python
 import waflib.Logs as Logs, waflib.Utils as Utils
 import os