www/rubygem-cssbundling-rails: Update to 1.1.2

Changes:	https://github.com/rails/cssbundling-rails/releases

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.

www: remove 'Created by' lines

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

  *
  *  <hvo.pm@xs4all.nl>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Dalton <aaron@daltons.ca>
  *  Aaron LI <aly@aaronly.me>
  *  Aaron Zauner <az_mail@gmx.at>
  *  Abel Chow <achow@transoft.net>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Adrian Steinmann <ast@marabu.ch>
  *  Akinori MUSHA aka knu <knu@idaemons.org>

www/rubygem-cssbundling-rails: Update to 1.1.1

Changes:	https://github.com/rails/cssbundling-rails/releases

www/rubygem-cssbundling-rails: Update to 1.1.0

Changes:	https://github.com/rails/cssbundling-rails/releases

www/rubygem-cssbundling-rails: Add rubygem-cssbundling-rails 1.0.0

Use Tailwind CSS, Bootstrap, Bulma, PostCSS, or Dart Sass to bundle and process
your CSS, then deliver it via the asset pipeline in Rails. This gem provides
installers to get you going with the bundler of your choice in a new Rails
application, and a convention to use app/assets/builds to hold your bundled
output as artifacts that are not checked into source control (the installer adds
this directory to .gitignore by default).

You develop using this approach by running the bundler in watch mode in a
terminal with yarn build:css --watch (and your Rails server in another, if
you're not using something like puma-dev). You can also use ./bin/dev, which
will start both the Rails server and the CSS build watcher (along with a JS
build watcher, if you're also using jsbundling-rails).

WWW: https://github.com/rails/cssbundling-rails