The suffix "Package", "Pck", or "Pkg" is useful to distinguish the auto-generated package unit from a "real" source unit.
Since many of our packages orginate from Delphi ancestors where they have a package file for every version, the prefix "laz" may be justified to highlight the Lazarus version in contrast to the Delphi versions, in addition to the extension. But your are right: the prefix usually is not necessary. I know I myself am guilty of some of these abuses. Is there a non-destructive way of renaming a package without breaking existing projects? And how does OPM handle the case that a package such as "laz_chemtext.lp", is renamed to "chemtext.lpk"? Will it remove the old "laz_chemtext" from the system when "chemtext" is installed? If not, the user will be in trouble because the contained component now exists twice.
I am a bit in doubt whether a grid which just implements a sorting method is justified to occupy a place in the component palette. Just for sorting if would be enough to put the Compare routine into a separate unit which might just be called to enable this feature in any existing string grid. (I did not have a too close look at TSortGrid, though).
In the long term I'd prefer a more general extended gird, not one just for sorting, to prevent cluttering the component palette of lots of dedicated grids.