Fix update time not being set when only drawable indexes are set

[TimSylvester]

When only a drawable's indexes are updated but not the vertex attributes, the update time wasn't set, and they were seen as out-of-date later on.

For OpenGL, changes to indexes didn't trigger an update at all, so that may have been leading to an un-detected bug. But the criteria for updates were also much too broad, so it was updating a lot when not really needed. I split up the check for building the indexes from the check for building the attributes, and saved the attribute bindings with the drawable so that they don't need to be re-built (by rebuilding the attributes) every time.

Resolves #2740

[github-actions]

Bloaty Results (iOS) 🐋

Compared to main

    FILE SIZE        VM SIZE    
 --------------  -------------- 
  [ = ]       0  [ = ]       0    TOTAL

Full report: https://maplibre-native.s3.eu-central-1.amazonaws.com/bloaty-results-ios/pr-2743-compared-to-main.txt

[github-actions]

Benchmark Results ⚡

Benchmark                                                     Time             CPU      Time Old      Time New       CPU Old       CPU New
------------------------------------------------------------------------------------------------------------------------------------------
OVERALL_GEOMEAN                                            -0.0041         -0.0044             0             0             0             0

Full report: https://maplibre-native.s3.eu-central-1.amazonaws.com/benchmark-results/pr-2743-compared-to-main.txt

[github-actions]

Bloaty Results 🐋

Compared to main

    FILE SIZE        VM SIZE    
 --------------  -------------- 
  -0.0% -3.62Ki  +0.0%    +336    TOTAL

Full report: https://maplibre-native.s3.eu-central-1.amazonaws.com/bloaty-results/pr-2743-compared-to-main.txt

Compared to d387090 (legacy)

    FILE SIZE        VM SIZE    
 --------------  -------------- 
   +27% +31.0Mi  +420% +25.1Mi    TOTAL

Full report: https://maplibre-native.s3.eu-central-1.amazonaws.com/bloaty-results/pr-2743-compared-to-legacy.txt

[louwers]

Would be good if @alexcristici or @mwilsnd can have a quick look as well.

Do you know why the failing assert was not triggered on CI?

[TimSylvester]

Do you know why the failing assert was not triggered on CI?

No, I can't explain that. Are you sure that asserts are enabled in the build that's running?