Answer
There's no single fixed naming pattern you can rely on (related projection and package names are usually recognizably similar, but not mechanically derivable from the projection name alone). The reliable way to find the actual package/Logical Unit behind any given Aurena page is to enable the 'Debug Console' option from the user menu in Aurena, which surfaces the real underlying Logical Unit and related metadata for whatever page you're viewing — once you have the LU name, identifying its corresponding API package becomes straightforward.