Fix some residual nondeterministic behavour in PyConf component names

The following discussion from !3789 (merged) should be addressed:

@sponce started a discussion: (+20 comments)

See last comment from @graven

This is not people declaring counters with the same name -- it is another example of Moore#484 (closed) where PyConf generated algorithm names are non-deterministic. @rmatev fixed most of problem some time ago in this MR, but there is still something left...

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information