Custom functions not tracked after restarting

### Version Information

Server Version:
CLI Version (for CLI related issue): 2.37.0

### Environment

local

### What is the current behaviour?

When i restart the hasura container using the hasura/graphql-engine:v2.37.0.cli-migrations-v3, custom functions that i have tracked before and show in metadata files (see screenshots) are untracked and i must manually add them back by clicking "TRACK"

### What is the expected behaviour?

It's expected that tracked custom functions would pull from metadata files

### How to reproduce the issue?

idk - sorry

### Screenshots or Screencast



### Please provide any traces or logs that could help here.

no errors. functions are just untracked

### Any possible solutions/workarounds you're aware of?

i am going to try calling the metadata API to reenable on startup

### Keywords

Custom Functions, Untracked

Start with the metadata files and metadata API, then reproduce the restart of the hasura/graphql-engine:v2.37.0.cli-migrations-v3 container. Compare the recorded custom functions with the functions shown as untracked after restart. Done means tracked custom functions are restored from metadata without manually clicking TRACK.

Written by the indexing model from the issue text.