Update not_null_proportion data test to use cross-database type_numeric() macro

[henriblancke]

resolves #553

This is a:

• bug fix with no breaking changes

Description & motivation

Checklist

• This code is associated with an Issue which has been triaged and accepted for development.
• I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
  • Athena
• I followed guidelines to ensure that my changes will work on "non-core" adapters by:
  • dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
  • using the limit_zero() macro in place of the literal string: limit 0
  • using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP
• I have updated the README.md (if applicable)
• I have added tests & descriptions to my models (and macros if applicable)
• I have added an entry to CHANGELOG.md

[henriblancke]

@joellabes would it be possible for you to take a look at his? Let me know if anything needs changing. Thanks!

[amacal]

@henriblancke would you try to fix conflicts and try again. I hope someone will merge it.

[github-actions]

This PR has been marked as Stale because it has been open with no activity as of late. If you would like the PR to remain open, please comment on the PR or else it will be closed in 7 days.

[github-actions]

Although we are closing this PR as stale, it can still be reopened to continue development. Just add a comment to notify the maintainers.

[dbeatty10]

Thanks for opening this @henriblancke !

The pre-existing tests are passing, so this looks good to me 👍