Update RPM spec file

Documentation files have been suffixed with ".rst".
Bug 1581: Avoid exception in LongOperationFeedback if desktop is not ready

FEA: ItEr77S04BugFixing
Bug #1587: Fix issue only resetting index of progress combo if it has items

FEA: ItEr77S04BugFixing
Bug #1583: If assignment function is not configurable keep button disabled

FEA: ItEr77S04BugFixing
Bug #1586: Fix issue reseting list of checkboxes before adding them

FEA: ItEr77S04BugFixing
Bug #1589: Fix issue using orderVersion for all the elements to be updated or added

FEA: ItEr77S04BugFixing
Bug #1590: Fix problem calling several times the same method in OrderModel

The problem was that OrderModel.getOrders() was been called several times to
show the list of projects.

After reviewing the problem several issues were detected:
* Util.createBindingsFor was always calling .loadAll() for each binder it
  creates, however this was not needed. Moreover a lot of times
  Util.reloadBindings is called just after Util.createBindings so the same thing
  is called twice.
* If you go via the entry point or the icon to the project list, the binder for
  the page is properly initialized or not. If you come from the entry point, the
  binder is already working as expected, however if you come from the icon the
  binder has to be created manually. It has been added a method
  CreatedOnDemandTab.afterCreateAction() that is called or not depending if the
  user comes from the entry point or the icon.

FEA: ItEr77S04BugFixing
Bug #1590: Avoid go to projects list when creating a project

FEA: ItEr77S04BugFixing
Bug #1590: Simplify Util.createBindingsFor

Fix 2 issues in Util.createBindingsFor:
* Avoid to go over all the children of the component as it seems enough with
  create the data binder in the root component.
* Avoid to call .loadAll() for each binder as the method Util.reloadBindings is
  usually used before when needed.

FEA: ItEr77S04BugFixing
i18n: Update keys.pot files

FEA: ItEr77S03Community
Bug #1592: Fix problem not showing the tab if it is already being shown

FEA: ItEr77S04BugFixing
debian: Add information about common issues in LibrePlan installation

FEA: ItEr77S03Community
Bug #1593: Fix issue translating the options while rendering

FEA: ItEr77S04BugFixing
Bug #1594: Fix issue opening transaction at DAO if needed

FEA: ItEr77S04BugFixing
Revert "Bug #1592: Fix problem not showing the tab if it is already being shown"

This reverts commit 8c6fb028e6921495cdb10d95245ac4199fa56b87.

It causes a NPE when adding tasks to a project just after create a project.
Revert "Bug #1590: Fix problem calling several times the same method in OrderModel"

This reverts commit 7ca0d43883d6ddc78f3346695867b2a94d5461d8.
Avoid some redundant loads of bindings in the same request

Sometimes reloadBindings is called several times in the same request.
Now only the first call would force the reload and the others would be
ignored.

For example, when switching to Projects List reloadBindings is called
after the tab being created and another time when calling
org.libreplan.web.orders.OrderCRUDController.goToList(). Now the
second call is ignored.
Bug #1590: Avoid repeated calls to goToOrdersList

A mechanism for ignoring in a scope the calls to createBindings has
been added. When accessing from the entry point the page is been
created and the AnnotatedDataBinder created automatically will track
the created tab. So in these cases we must ignore createBindings
calls.
Bug #1592: Save Order before showing it

Otherwise the MutableTreeModel associated is initialized with a Order
that is not saved yet. When it's used, e.g., when adding a
subtask, it fails.

The MutableTreeModel#nodesByDomainObject map wouldn't find the node
associated to the Order, because the hashCode is different. At first
the Order is a new object so it returns a different hashCode, once
saved another. With these changes, when initializing the
MutableTreeModel it has already been saved.
Bug #1592: Fix problem not showing the tab if it is already being shown

FEA: ItEr77S04BugFixing