Currently debugging #86 but the file is impossible to read...

These changes create instability on development images in
conjunctio with mount for core.git:  since files move they
exist in two places at once, maybe screwing up the system.
There's no sensible way other than asking for or building
a new snapshot package for opnsensense and going from there.

Seeing PHP ignore text files makes it easier to lint over more
files for a simple reason:  maybe someone sneaked a PHP file
into the repo and forgot the proper file extension, which is not
uncommon for utilities in *bin/ -- makes it easier to catch those.

* We can now see the errors we suppress.  E_WARNING is the one that
  should be zapped as soon as possible.

* According to the manual, display_startup_errors should not be enabled.

* Add ignore_repeated_errors to avoid multiple reports in e.g. loops.

While there, don't expose the main include file to the web server.

(1) It has been disabled since our first release.
(2) It is not part of our development workflow.
(3) It is quite dangerous and potentally fatal.

Quality is important; we hide PHP warnings so it's good to let
our beloved users/testers check and forward them regularly.  :)

* add E_PARSE to show proper info about parse errors
* remove PHP 5.5 support, we've never shipped it
* fix textarea display width and disable send button

Move the config files out of the way, but still install them properly.

Just rewrite that stuff completely...  Pretty simple now, right?  :)

We now use /usr/local/opnsense/version/xxx as our version database.
Apart from the core package, opnsense-update(8) also puts its own
version information in there.  To stay somewhat consistent, the
version file should resemble the package name, even though that
looks strange in our case: /usr/local/opnsense/version/opnsense.
It's just that /usr/local/etc is too open and might clash with
other things in the future.

We don't have OpenSSH in base anymore so we can zap the fallback.
And since openssh-portable is a direct dependency of opnsense, we
can be pretty sure it'll be there.

Discussed with: @deZillium (Twitter)