fix: Pavex always uses a public path to refer to public items, even if they are defined in a private module

fix: Pavex always uses a public path to refer to public items, even if they are defined in a private module #441