Refactor InApp logic from Stack Traces

[lucas-zimerman]

This replaces the hardcoded logic to decide if the Frame is InApp or not by the one used by the main SDK.

One question was raising during the development of this PR

Should we add the code
System.Diagnostics.Debug.Fail("This UnityLogException constructor should not be used, please use the one that gives the SentryOption as an argument.");

On

        internal UnityLogException() : base()
        {
            LogString = "";
            LogStackTrace = "";
        }

        private UnityLogException(string message) : base(message)
        {
            LogString = "";
            LogStackTrace = "";
        }

        private UnityLogException(string message, Exception innerException) : base(message, innerException)
        {
            LogString = "";
            LogStackTrace = "";
        }

Since they are not intended to be use by us?

Close #575

[bruno-garcia]

Could you please add some tests with InAppInclude and InAppExclude?

[bruno-garcia]

Or at least showing the Mono inApp thing now is fixed

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Refactor InApp logic from Stack Traces ([#661](https://github.com/getsentry/sentry-unity/pull/661))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 5f37860