this gets rid of a warning when a mode isn't properly defined

this removes a few evil hooks

* Made sure all electoral list functions are together and are prefixed by electoral_list_
* Changed decisions_tab_something-like functions to decisions_something_tab
* In decisions_datetime.inc, prefixed the decisions_translate_form_date() function with an underscore

* All non-API functions prefixed with an underscore and should be at the end
* Theme functions grouped together
* Grouped functions by category (API, theme, electoral list, mode-related, callbacks, internal)

In function _decisions_algorithm(), check if the returned list of algorithms is okay and print a warning if not.

- Handles the functionalities of start and close dates through two new functions "decisions_can_vote()" and "decisions_is_open()"
- Prints status messages at the top of the node view to inform the user about quorum/can vote/is open isues
- Adds a theme_decisions_status() function to print status messages such as "This decision is not yet opened."
- Modifies the decisions_view_vote_counts() to print date information; renames the function to theme_decisions_view_header()

Adds a "no end date" checkbox to specify an infinite voting period (no closing date). Still not operational, only saves it properly in the DB.

* Replace the "duration" select box by a "Closing date" widget.
* Add a "Start date" widget.
* Does not change the current fields in the DB whatsoever.
The plan is to reintegrate the duration as an option later on (like, you'd be able to choose between a closing date or a duration). This patch merely handles the saving/loading of those values: it still does not affects the behavior of the decision.

votes" instead of "administer decisions" since it can be deduced from
"all votes" anyways and users might want to give access to this
analysis to others than admins

taken from #98603

doesn't work, as the choice fieldset seems to force its children to be
integer-indexed. it also doesn't blend very well with the way we
handle choices to add non-choices items in there.

= 0 being added at the end

the poll validation function was also returning false in some corner
cases when the form didn't have errors

fix one of those issues (bad quoting in view_results())

decisions_hook_foo()

there remains weird functions in ranking.inc I need to fix

original patch

from tatien

  apply patch #92976 from tatien: change the (apparently obsolete)
  VOTINGAPI_VALUE_TYPE_KEY constant for 'option' and fix other problems
  with $vote objects not being created.

a permission for removing voter, probably due to a bad merge from advpoll

VOTINGAPI_VALUE_TYPE_KEY constant for 'option' and fix other problems
with $vote objects not being created.

 - import javascript fixes from advpoll
 - hide the "Need more choices" button for javascript-enabled clients
 (since we now have a dynamic "add choice" button): #93939
 - put maxchoices in the choices fieldset
 - create a seperate fieldset for quorum
 - improve quorum descriptions