release-post-assemble error

Why is this change being made?

When the release post manager runs bin/release-post-assemble as part of the process to prepare the release post, this error appears:

/Users/user/Development/GitLab/www-gitlab-com/lib/release_posts/post.rb:85:in `block (2 levels) in update_deprecations': undefined method `config' for nil:NilClass (NoMethodError)
        from /Users/user/Development/GitLab/www-gitlab-com/lib/release_posts/post.rb:84:in `each'
        from /Users/user/Development/GitLab/www-gitlab-com/lib/release_posts/post.rb:84:in `block in update_deprecations'
        from /Users/user/Development/GitLab/www-gitlab-com/lib/release_posts/post.rb:81:in `each'
        from /Users/user/Development/GitLab/www-gitlab-com/lib/release_posts/post.rb:81:in `update_deprecations'
        from /Users/user/Development/GitLab/www-gitlab-com/lib/release_posts/post.rb:41:in `assemble'
        from bin/release-post-assemble:6:in `<main>'

It's a non-blocking error, but it often causes confusion.

This MR will allow the error to fail silently so as not to disrupt the release post manager's progress.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---