It is not there. At least, not in the way avil meant.
The current foreign key feature is already extremely useful, especially if you use UUID based primary keys.
The suggested foreign key feature is to be able to continue the process and thus ‘navigate’ through the database.
Suppose a database schema with a Document referencing a User referencing an Organisation referencing an Address.
With the current feature, you cannot go from Document to Address without copy-pasting the intermediate foreign keys in some filter. It only works for inspecting records that are one step away.
With the suggested feature, one would be able to open the referenced table (with filter enabled) in a view in which you can consequently open other FK references and continue the process indefinitely.
I do believe the original implementation should also be accessible, as it is useful for assigning a value (and I don’t see how such functionality could be implemented naturally if the result is shown in a separate table data view or in the query result view).
