[BUG] CMAIZE_PROJECT does not contain the correct project after including CMaize dependency

[zachcran]

Describe the bug
CMAIZE_PROJECT does not contain the correct CMaize project after a call to cmaize_find_or_build_dependency() that pulls in another project built with CMaize. This bug was brought to our attention in NWXCMake issue 12.

To Reproduce
Steps to reproduce the behavior:

1. Create dummy projects A and B, where B depends on A using cmaize_find_or_build_dependency().
2. Build B, printing the name of the CMAIZE_PROJECT object before and after the cmaize_find_or_build_dependency() call.
3. These names should be the same (both should be project B) before and after the dependency is pulled in.
4. Instead, before project A is built in, the CMAIZE_PROJECT name is correct, but after project A is pulled in, CMAIZE_PROJECT will contain project A.

Expected behavior
After pulling in project A, the context-dependent CMAIZE_PROJECT variable should contain project B again.

Additional context
For now, this can be worked around by getting the CMAIZE_PROJECT_${PROJECT_NAME} variable instead. This will get the CMAIZE_PROJECT object associated with the current project. Any CMaize project can be obtained using this method by getting CMAIZE_PROJECT_<desired_project_name>.