[MOV] content/*: move resource files into their related page's directory

Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.

For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:

├── parent_doc/
│     └── doc1/
│     │     └── image.png
│     │     └── download.zip
│     └── doc1.rst
│     └── doc2.rst
├── parent_doc.rst

Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.

In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.

task-2497965

Part-of: odoo/documentation#2026

content/developer/reference/javascript/mobile.rst

@@ -26,7 +26,7 @@ How does it work?
 
 Internal workings of the mobile application:
 
-.. image:: images/mobile_working.jpg
+.. image:: mobile/mobile_working.jpg
 
 Of course, it is a web page that loads on a Mobile Native Web container. But it
 is integrated in such a way that you can access native resources from your web
@@ -50,7 +50,7 @@ How to use it?
 Just like the Odoo Web Framework, the Mobile API can be used anywhere by getting the object from
 **web_mobile.rpc**
 
-.. image:: images/odoo_mobile_api.png
+.. image:: mobile/odoo_mobile_api.png
 
 The mobile RPC object provides a list of methods that are available (this only works with the mobile
 app). 
@@ -78,7 +78,7 @@ remains visible and interactive.
 
 	mobile.methods.showToast({'message': 'Message sent'});
 
-.. image:: images/toast.png
+.. image:: mobile/toast.png
 
 
 Vibrating device
@@ -119,7 +119,7 @@ displayed at a time.
 		}
 	});
 
-.. image:: images/snackbar.png
+.. image:: mobile/snackbar.png
 
 Showing notification
 .....................
@@ -139,7 +139,7 @@ view at any time.
 	
 	mobile.showNotification({'title': 'Simple Notification', 'message': 'This is a test for a simple notification'})
 
-.. image:: images/mobile_notification.png
+.. image:: mobile/mobile_notification.png
 
 
 Create contact in device
@@ -173,7 +173,7 @@ Create a new device contact with the given contact details.
 
 	mobile.methods.addContact(contact);
 
-.. image:: images/mobile_contact_create.png
+.. image:: mobile/mobile_contact_create.png
 
 Scanning barcodes
 ..................
@@ -208,4 +208,4 @@ Use switchAccount to switch from one account to another on the device.
 	
 	mobile.methods.switchAccount();
 
-.. image:: images/mobile_switch_account.png
+.. image:: mobile/mobile_switch_account.png