Support Ruby 3.0.3

[jrgriffiniii]

This is derived from samvera/maintenance#77

[jrgriffiniii]

49c0f0d finally ensures that bundle install can reliably install Gem dependencies, however the following psych bug is now raised:

An error occurred while loading ./spec/integration/associations_spec.rb.
Failure/Error: fedora_yml = YAML.safe_load(config_erb, [], [], true) # allow YAML aliases

ArgumentError:
  wrong number of arguments (given 4, expected 1)
# ./vendor/bundle/gems/psych-4.0.3/lib/psych.rb:323:in `safe_load'
# ./lib/active_fedora/file_configurator.rb:111:in `load_fedora_config'

[jrgriffiniii]

For releases of ldp following 0.4.1, Ruby 2.y.z releases are required (please compare https://rubygems.org/gems/ldp/versions/0.4.1 and https://rubygems.org/gems/ldp/versions/0.5.0)

[jrgriffiniii]

The method signature for https://github.com/ruby-rdf/rdf/blob/develop/lib/rdf/model/graph.rb#L106 has changed, and https://github.com/ActiveTriples/ActiveTriples/blob/develop/lib/active_triples/rdf_source.rb#L125 must be updated for this.

[jrgriffiniii]

This is also blocked by another release of ldp:

active-fedora was resolved to 13.2.7, which depends on
      ldp (>= 1.0) was resolved to 1.0.3, which depends on
        Ruby (~> 2.0)

[jrgriffiniii]

55ef06e seems to still be blocked until I can port Lando for running the test suites.

[jrgriffiniii]

https://github.com/samvera/active_fedora/compare/updating-active-triples?expand=1 advances this with as much labor as I can provide before the next scheduled Developer Congress.

[jrgriffiniii]

POST requests are submitted with erroneously-formatted parameters:

"\n [info:fedora/fedora-system:def/model#hasModel "Image"] .\n

These brackets should not be present here.

[jrgriffiniii]

c53f863 ensures that nodes for ordered list nodes can be resolved from LDP servers.

[jrgriffiniii]

4029315 was needed as a starting point for me to understand why Proxy models are not being resolved from ListSources when ActiveFedora::Base#reload is invoked (they are persisted, but for some reason, the cache for these is not repopulated for the Associations).

[jrgriffiniii]

e629829 is a potential solution, but I am still struggling to understand why this was breaking with a simple Ruby/Rails upgrade.

[jrgriffiniii]

49c1203 was needed to address certain cases where duplication was occurring, but this does not seem to correctly address the cases for ordering elsewhere.

[cjcolvar]

Draft PR: #1489 waiting on ActiveTriples support for ruby 3.