Need registry for make_hpge

[tdixon97]

We always need to supply a registery for make_hpge and you get errors if you make the same HPGe twice. This is a bit annoying when you want to access just some methods of HPGe not use it in geometry. Maybe we could make this optional?

[gipert]

#61

[ManuelHu]

In the past, the registry parameter was optional.

And it (sadly) created quite some problems, when using those objects with no registry in a full geometry. Mainly it skipped duplicate-name checks, which could lead to objects being skipped while being written out to GDML - whithout warning or error message. This is a limitation of how pyg4ometry works internally.

The option I implemented back then is to require an explicit registry=None parameter to ensure the user is aware what they are doing. I do not have a better idea how to fulfill this requirement in any other way.

for reference: #59, #60, #61, g4edge/pyg4ometry#216

[tdixon97]

Sorry I forgot the option to pass None this should be totally ok for reboost so we can close this