Allow users to not include macros in their coverage report

[ksew1]

Users may not want to include code generated by macros in their coverage report, as they often can't modify the output produced by them. Currently, we can't distinguish between inline macros, attribute macros, and derive macros; this should change in #44. For now, we can add option to include all macros or exclude all of them.

Additionally, we need to redesign our CLI so we don't need to add another flag like --include-macros, as this can possibly create more conflicts. Currently, there are two components that can be included: test functions and macros. We will create a flag named --include that will take a list of additional components that should be included in the coverage report.

CLI Usage Example

cairo-coverage --include test-functions macros