Use Gitlab::ErrorTracking track & raise vs. logger

What does this MR do?

Issue #232654 (closed)

I noticed when testing the previous MR for this issue in production that the logging is not showing up in Kibana. I have not been able to reproduce the issue causing this locally so have only been able to test with Unit tests. The documentation recommends using Gitlab:ErrorTracking.track_and_raise_exception in place of manual logging. Using this method should pass the extra data along to Sentry (project_id) that is needed to help figure out what is causing the null project_feature objects.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team