fix subprofile name in profile serialization

Given the following profile:

profile foo { profile bar { profile baz { } } }

The parser would correctly serialize the "foo" profile and the "foo//bar" profile, but it would incorrectly name "bar//baz" when it should be "foo//bar//baz". This would cause issues loading the profile in certain kernels causing a "parent does not exist" error.