Optimizing read_geopkg function

[AminTorabi-NOAA]

This PR improves the speed of read_geopkg function, with below changes. :
(It improve the Duration by 20% and CPU Time by 50%)

1. Optimized Parallel Processing.
   Used min(cpu_pool, len(layers)) to ensure we don't create more parallel jobs than layers, which avoids unnecessary overhead.

2. Reduced Repetition:
   Removed repeated code for reading layers by creating a read_layer function.

3. Ensured Efficiency:
   Removed unnecessary list creation and directly accessed the table_dict.

Additions

Removals

Changes

Originally it was taking 2.47 sec

after the changes it takes 1.96 sec which is 20% improvement:

Testing

Screenshots

Notes

Todos

Checklist

• PR has an informative and human-readable title
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (link if applicable)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• Visually tested in supported browsers and devices (see checklist below 👇)
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Testing checklist

Target Environment support

• Windows
• Linux
• Browser

Accessibility

• Keyboard friendly
• Screen reader friendly

Other

• Is useable without CSS
• Is useable without JS
• Flexible from small to large screens
• No linting errors or warnings
• JavaScript tests are passing

[shorvath-noaa]

I think we need to drop the "paths" here. I believe these can be called "flowlines" which this would not find.

[AminTorabi-NOAA]

I think if we drop the "paths" and make it to just look for "flow" it will find both "flowpaths" layer and "flowpath_attribute" layer. I just added "flowlines" too, that should solve the problem

[shorvath-noaa]

Great. Can you do the same for flowline-attributes? I'm not sure if that's a potential table name, but we might as well cover our bases.

[AminTorabi-NOAA]

Sure. Just added