docs: Add link to eval blog

[mikemckiernan]

Description

Aditi's blog supplements the eval information we have in the docs for input and output rails.

Related Issue(s)

Checklist

• I've read the CONTRIBUTING guidelines.
• I've updated the documentation if applicable.
• I've added tests if applicable.
• @mentions of the person or team responsible for reviewing proposed changes.

[github-actions]

Documentation preview

https://nvidia.github.io/NeMo-Guardrails/review/pr-1180

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.24%. Comparing base (b65cf0e) to head (3dfbbc4).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1180   +/-   ##
========================================
  Coverage    68.24%   68.24%           
========================================
  Files          161      161           
  Lines        15938    15938           
========================================
  Hits         10877    10877           
  Misses        5061     5061           

Flag	Coverage Δ
python	68.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[trebedea]

Hi @mikemckiernan ,

Actually the evaluation documentation probably needs a bit of changes. Right now we have two different type of evaluation tools and corresponding documentation :

1. An eval tool and docs mainly intended for researchers and it shows how to evaluate individual rails (e.g. dialogue, content moderation, fact-checking). This is the documentation you are changing in the current commit.
2. An end-to-end evaluation for guardrail configs that support different rails, this is also called policy-based evaluation. The docs for this eval tools are here: docs/user-guides/eval/methodology.md

The mention to the blog post should be done in the docs for #2, no?
Any restructuring ideas for these two eval tools and documentation would also be useful.

Thanks!