VCS plugins changes:
- SourceGithub 2.3.1

Will fix these later

VCS plugins changes:
- SourceSFSVN 2.1.1
- SourceViewVC 2.1.1
- SourceVisualSVNServer 2.1.1
- SourceWebSVN 2.1.1

Caused integration plugins derived from SourceSVN, i.e.
- Source Subversion / SourceForge (SourceSFSVN)
- Source VisualSVN Server (SourceVisualSVNServer)
- Source Subversion / WebSVN (SourceWebSVN)
- Source Subversion / ViewVC (SourceViewVC)

to show Source Subversion Integration as an outdated dependency in the
Manage Plugins page.

Fixes #388

VCS plugins changes:
- SourceAzureDevOps 1.0.0 (new)
- SourceBitBucket 2.2.0
- SourceCgit 2.1.0
- SourceGithub 2.3.0
- SourceGitlab 2.1.0
- SourceGitphp 2.1.0
- SourceGitweb 2.1.0
- SourceHgWeb 2.2.0
- SourceSFSVN 2.1.0
- SourceSVN 2.4.0
- SourceViewVC 2.1.0
- SourceVisualSVNServer 2.1.0
- SourceWebSVN 2.1.0

- Update copyright year
- Reformat version compatibility table.

Signed-off-by: Damien Regad <dregad@mantisbt.org>

Fixes #369

Signed-off-by: Damien Regad <dregad@mantisbt.org>

Fixes #387

Signed-off-by: Damien Regad <dregad@mantisbt.org>

The extra <span> tag added by the libravatar plugin triggered a value
too long for type character varying(250) error.

Modified regex to cover this use case.

Use a variable for the pattern to avoid code duplication.

Fixes #386

Changes to original contribution:
- reworded commit message
- added non-capturing regex group for the <span> tag
- coding guidelines

Signed-off-by: Damien Regad <dregad@mantisbt.org>

Occurred when importing data

Fixes #149, #165

Signed-off-by: Damien Regad <dregad@mantisbt.org>

Changes to original contribution:
- coding guidelines
- rewritten commit message

Signed-off-by: Damien Regad <dregad@mantisbt.org>

When creating a new webhook, Github delivers a ping event [1] which is
treated as an error by the plugin, which returns HTTP 400 "Changeset
information could not be loaded".

We now detect that the payload is a ping event, and return an HTTP 200
status code with an information message.

Fixes #382

[1] https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#ping

Information such as passwords, client secret, application tokens, etc.
should not be displayed in plain text.

- on repo_manage_page.php, display data as `•••••`
- on repo_update_page.php, use inputs of type password

Fixes #329

When updating Github repo with empty client id/secret, PHP issues
"Undefined array key" warnings.

Fixes #383

Also adjust table row headers' markup on Bitbucket repo update form,
which formatted incorrectly following d6e6c233.

Fixes #317

Add new SourceChangeset::getLocalTimestamp() method, that both formats
the timestamp and converts it to local time.

Use it in view.php and Source_View_Changesets() function.

Fixes #317

Some VCS plugins used the date() function to pass a formatted Changeset
timestamp to the SourceChangeset constructor. This caused conversion to
the user's timezone, leading to inconsistent behavior when saving the
Changesets to the database.

Note: the timestamp column is defined as datetime, not timestamp, so
timezone information is not persisted.

To ensure consistent behavior of Changeset timestamps, we store them as
a DateTimeImmutable object in SourceChangeset, instead of a string
without timezone information.

This is a workaround for a bug in Bitbucket API [1][2] which returns a
"Resource not found" error when the branch has a '/' in its name.

If the initial commit is a branch name containing a slash, we now look
up the target commit SHA using the refs/branches API endpoint before
entering the main processing loop.

Fixes #376

[1]: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-commits/#api-repositories-workspace-repo-slug-commit-commit-get
[2]: https://jira.atlassian.com/browse/BCLOUD-9969

When updating the Primary branches list with a branch containing a /,
the plugin was throwing a generic APPLICATION ERROR.

Using the standard git branch validation method instead.

Fixes #381

Regression introduced in 3bac7d4a.

Add error handling in import_full() to display a meaningful message
when the Gitlab API call did not return any data.

Also add a basic URL sanity check in repo_update_page, displaying a
warning sign when the given string fails a filter_var() URL validation.

Fixes #373

When the repo is first updated after initial creation, update_repo()
throws a SYSTEM WARNING, as hub_reponame is not yet defined when we
check its value to set $f_hub_repoid.

Issue #352

Function was introduced in #215 to fix the problem in the plugin, until
the update was implemented in MantisBT core (which happened in 2.24.0).

Fixes #339

This is required so we can remove the plugin_lang_get_defaulted()
function, duplicated from plugin API (see #339).

Fixes #337

Commit 284e9370 introduced a regression
on the display of input fields's captions, which were no longer in bold
font when a <label> tag is used.

Changing the <td> to <th> to fix the problem.

Trying to detach an Issue from a Changeset always results in
APPLICATION ERROR 2800 - Invalid form security token, even when using
a valid token.

This is because print_form_button() currently does not work with action
URLs generated by plugin_page(), see [1].

So we revert to original behavior of using print_small_button() (as it
was before commit 787eaa84), but keeping
the single form security token implemented in commit
634277d2.

This change can be reverted again, once the upstream issue has been
fixed.

Issue #372

[1]: https://mantisbt.org/bugs/view.php?id=28533