Add package orderers documentation

[BryceGattis]

Looking for some feedback on what exactly this page should look like. Some examples of the configuration are on the configuring rez page, but I'm not sure if we want the same kind of info here or not.

[JeanChristopheMorinPerso]

It's a good start. I made small comments that shouldn't be too difficult to address.

We should also be careful to not drop or have duplicated information with https://rez--1737.org.readthedocs.build/en/1737/configuring_rez.html#package_orderers.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.30%. Comparing base (491497f) to head (3012900).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1737   +/-   ##
=======================================
  Coverage   59.30%   59.30%           
=======================================
  Files         126      126           
  Lines       17210    17210           
  Branches     3015     3015           
=======================================
  Hits        10206    10206           
  Misses       6319     6319           
  Partials      685      685           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JeanChristopheMorinPerso]

@BryceGattis I pushed some changes. When you have a minute, could you take a look and tell me if what I wrote is clear please?

[BryceGattis]

@JeanChristopheMorinPerso The changes you made were great thank you. The one lingering question I have is that I'm still not fully understanding the purpose of the per_family orderer. If every other type of orderer (ex. sorted), can have a packages attribute (and therefore can filter by package families), what is the purpose of the per_family orderer?

[BryceGattis]

@JeanChristopheMorinPerso What do you think about having a glossary for rez? I was just thinking that a clickable link for package family would be nice. Perhaps the definition of a package family could just live in the Getting started or Basic Concepts pages though instead of making a new glossary page.

[JeanChristopheMorinPerso]

Thanks @BryceGattis for taking some time to look at my changes! I agree that we need a glossary, but I think this can be done in a separate PR.