stop using local_rels/attrs in schema update

[ajtmccarty]

IFC-1090

made a followup issue to remove duplicated inherited relationship/attribute data from the database: IFC-1201

loading an extension of a schema that inherits a relationship from a generic can cause the inherited relationship on the schema to be deleted.

the code seems to indicate that we assume a given SchemaNode in the database will only have its non-inherited ("local") relationships linked and will NOT have any inherited relationships, but this is not how it actually works at the database level. a SchemaNode will be connected to SchemaRelationships for every one of its relationships, whether they are inherited from a generic or not

an example from the database
the red path is for the interfaces relationship on a generic schema and the green path is for the inherited interfaces relationship on a node schema. both the SchemaGeneric and SchemaNode include this relationship even though it is only defined on the generic

my fix for this issue is to consider all relationships and attributes when updating a schema for a node instead of just the inherited/local ones. this does fix the problem, but I am worried that there may be side effects that are not covered by our current test suite b/c we don't have a lot of tests for loading/updating schema

[codspeed-hq]

CodSpeed Performance Report

Merging #5595 will not alter performance

_{Comparing ajtm-01272025-generic-extensions-bug (d54ddf3) with stable (be13145)}

Summary

✅ 11 untouched benchmarks

[LucasG0]

Changes seem to affect any node update, not specifically a node loaded through extensions, it makes me wonder:

• Would these changes also fix other cases not related to extensions?
• Or should the fix be located around some extensions related code?

I am not familiar with extensions schemas though