Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby

Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk

Notable changes are.

- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
  USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.

This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863

I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.

Approved by:	portmgr
Differential Revision:	https://reviews.freebsd.org/D37925

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

security: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Aldis Berjoza <aldis@bsdroot.lv>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alex Kapranoff <kappa@rambler-co.ru>
  *  Alex Samorukov <samm@freebsd.org>
  *  Alexander Botero-Lowry <alex@foxybanana.com>
  *  Alexander Kriventsov <avk@vl.ru>
  *  Alexander Leidinger <netchild@FreeBSD.org>

Remove # $FreeBSD$ from Makefiles.

Update to 0.2.8

Changes:	https://gitlab.com/satorix/omniauth-oauth2-generic/-/commits/master

Update to 0.2.7

Changes:	https://gitlab.com/satorix/omniauth-oauth2-generic/-/commits/master

Update to 0.2.6

Changes:	https://gitlab.com/satorix/omniauth-oauth2-generic/-/commits/master

Update to 0.2.5

Changes:	https://gitlab.com/satorix/omniauth-oauth2-generic/-/commits/master

Update version requirement of RUN_DEPENDS

Update to 0.2.4

Changes:	https://gitlab.com/satorix/omniauth-oauth2-generic/blob/master/CHANGELOG.md

Update to 0.2.3

Changes:	https://gitlab.com/satorix/omniauth-oauth2-generic/blob/master/CHANGELOG.md

Add rubygem-omniauth-oauth2-generic 0.2.2

omniauth-oauth2-generic provides an OmniAuth strategy for authenticating with an
OAuth2 service using the authorization grant flow.

Most OmniAuth gems are written either as abstractions (omniauth-oauth2) or for a
specific provider (omniauth-github), but this one is designed to be configurable
enough to work with any basic OAuth2 provider. The primary differences between
OAuth2 provider strategies in OmniAuth are:
- The server's domain
- The URL paths used to authorize, request tokens and get user info
- The structure of the returned user information

These are all configurable options in this gem. There my be certain
requirements/features of some providers not covered by this gem's options, but
it was designed primarily so that if you are implementing your own OAuth2
provider for your service, you don't need to write an OmniAuth strategy as long
as it is compatible with the basic options provided by this gem.

WWW: https://gitlab.com/satorix/omniauth-oauth2-generic