Improve display of repository 'Extra Info' field

Instead of a foreach loop and individual call to var_dump() on each
element of the info array, we now call var_dump() on the array itself,
so that the displayed information is more easy to read.
Replace uses of config_get() by calls to plugin_config_get()
Partial revert "Replace uses of config_get() by calls to plugin_config_get()"

This partially reverts commit 9222599ab5f04615763262a0b8784d40cf7a2590.

It is required that we use config_get() referencing the 'Source' plugin
in SourceIntegration.php. Because SourceIntegration is a child plugin of
Source, plugin_config_get() does not refer to the correct config string
when retrieving the setting, causing 'Configuration option not found'
errors to occur.
Added option to select view state of bug notes

Prior to this, the 'Bug fix' notes view state was hardcoded to public.
We are now allowing the administrator to choose whether they should be
public or private by means of a config option.

Fixes #42

Cyril's original commits were squashed.

Signed-off-by: Damien Regad <damien.regad@merckgroup.com>
Use Selection list to pick bugfix notes view state

To be consistent with MantisBT core, the bugnote view status is now set
by means of a selection list (i.e. pick public/private) instead of a
checkbox.
Added explanatory text for private bugnotes setting

bugnote_add() API will force VS_PUBLIC state if changeset's author does
not have private_bugnote_threshold.
Move text formatting for some language strings to config page
Updated French translations
WebSVN: minor adjustments (coding guidelines, whitespace)
WebSVN: add 'sc' option to base_url() function

The 'sc' (show change) option is obsolete since WebSVN 2.1.0 (r621)
we keep it for Compatibility with oder releases. Refer to discussion on
Github [1].

[1] https://github.com/dregad/source-integration/pull/1#commitcomment-2711137
WebSVN: multiview support and other enhancements

Fixes #46, #47
Fix #51: Fixed Issues are always set to Resolved status

Prior to this, whe plugin would always set a fixed issue's status to
Resolved, regardless of how the the "Resolve Fixed Issues" option
(plugin_Source_enable_resolving) is set in the config page.
oops

I was a bit too trigger-happy with the search/replace in commit
250c07917cb74afdfe29b5e73b18b753e7315ee1