Refactor: create trace.py

[dianzrong]

What kind of change does this PR introduce?

Refactoring

Summary

Refactor the trace code from record.py to trace.py. Addresses #387

Checklist

• My code follows the style guidelines of OpenAdapt
• I have performed a self-review of my code
• If applicable, I have added tests to prove my fix is functional/effective
• I have linted my code locally prior to submission
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
• New and existing unit tests pass locally with my changes

How can your code be run and tested?

Can be tested through running record.py

[angelala3252]

some small things, otherwise looks good!

[abrichr]

@dianzrong can you please fix merge conflicts and add a test?

At a minimum we want a smoke test that looks like, e.g.:

def test_trace():
    @trace()
    def foo():
        pass

If you really want to you can simulate some function calls and look in stdout to make sure the calls are logged but it's not necessary.