Fixing Fcls for the New Geometry Handling

[jzennamo]

Description

I have updated three fcls that needed to have their Geometry Service connections updated to address the new LArSoft refactoring for the v10 transition

Checklist

• Added at least 1 label from available labels.
• Assigned at least 1 reviewer under Reviewers,
• Assigned all contributers including yourself under Assignees
• Linked any relevant issues under Developement
• Does this PR affect CAF data format? If so, please assign a CAF maintainer (PetrilloAtWork or JosiePaton) as additional reviewer.
• Does this affect the standard workflow? Yes!

Relevant PR links (optional)

Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?

This is based off feature/geom

Link(s) to docdb describing changes (optional)

Is there a docdb describing the issue this solves or the feature added?

Not yet.

[PetrilloAtWork]

Not an expert on this new geometry, but it seems to me your changes are consistent with the rest of the branch.
But I would suggest to create a geometry configuration table in geometry_sbnd.fcl bundling all this stuff together, something like:

geometry_services_sbnd: {
  GeometryConfigurationWriter: {}
  Geometry:                    @local::sbnd_geo
  WireReadout:                 @local::sbnd_wire_readout
  AuxDetGeometry:              @local::sbnd_auxdetgeo
}

so that configurations can get away with just

services: {
  # ...
  @table::geometry_services_sbnd
  # ...
}

Note that if this approach had been already adopted, this PR would not have been necessary at all.

[jzennamo]

@PetrilloAtWork this is a fair suggestion, maybe we can consider this as part of a future PR.

@wjdanswjddl I tested these fcls on data directly and they worked!

[bear-is-asleep]

Approved, this is a PR directly to another feature branch.