I’m checking to make sure my mental model for the Ignition 8.3 config experience is correct.
Our module has registered its own configuration page under the Connections section (Seeq > Settings).
I noticed that under the Platform section, there’s also an entry for “Seeq Settings” and I’m not sure what causes that. Should I do something in my module code to remove that? Or do something to cause a “Configure” hyperlink to appear on the right?
Okay, so there's a few concepts to unpack here.
Most fundamentally, what you're looking at on the "Overview" page is surfaced by the new to 8.3 EntityManager API.
As mentioned in the Javadoc there:
NOTE: the entity system is automatically aware of the configuration Resource system. Any resources that have a
ResourceTypeMetaregistered will automatically be included in the configuration entity.
That's why you have an entry automatically.
It looks like the link to the configure section is attached to whether your Category definition has is providing a set of ResourceTypes - which it isn't unless you've changed the code since you posted it here: Ignition 8.3: Controlling placement of nav entries 
That default behavior, linking based on associated resource types, is ultimately decided by the DefaultResourceEntityDelegate we're creating for you in DefaultResourceTypeMeta.Builder - if you don't provide or customize one, the no-arg constructor of the default resource entity delegate is used, but you can also provide your own or customize it via withEntityDelegate or buildEntityDelegate on your type meta builder.
The general recommendation is to have it show up on the platform overview page (which is deliberately meant to be "absolutely everything on this particular gateway"), with customization as needed to tweak the behavior.
