A Localisation Record is created when submit a expense record
only one received localisation record per user

erp5_travel_expense: localisation search should not prevent image preview

erp5_travel_expense: make sure localisation gadget is loaded

erp5_travel_expense: don't create localisation record when location is undefined

erp5_travel_expense: naming convention

erp5_travel_expense: Have Projects availables in Expense, define group on images and set source_section

erp5_travel_expense: Improve Front page and fix CSS on image modal

erp5_travel_expense: Router redirect to front page

erp5_travel_request: Add missing Preference PropertySheet

erp5_travel_expense: Add mission Administration

erp5_travel_expense: Add missing category

erp5_travel_expense: Make Expense document publication customizable by script

erp5_travel_expense: Add mission jio_view action on Service

erp5_travel_expense: Also remove Title from expense view in app

erp5_travel_expense: Remove all form of titles

erp5_travel_expense: Add transactions view on Expense Validation, Fix/Update  transaction generation

erp5_travel_expense: avoid undefined value

erp5_travel_expense: link related to Travel Request instead of record

erp5_travel_expense: can use listbox to search related mission in expense record

This was only used by listbox.
As most fields now render themself as 'p' tag in non editable mode, they are compatible with non editable listboxes to be rendered inside an 'a' tag.