update fusesoc fork to modern fusesoc?

[Kreijstal]

Description

The fusesoc version is ancient, is there a particular reason for this? Wouldn't it be better if it was more up to date? 0.1 was long time ago, we are now at 2.3

[hcallahan-lowrisc]

Hi @Kreijstal, you can see some of the previous discussion about moving to upstream fusesoc in this issue #20379, but we're currently still dependent on some custom features in our fork of fusesoc. Rather than just bumping the fork version (and the work needed to rebase our custom features), it would be more desirable to get back to upstream, and re-implement those custom behaviours using newer upstream abstractions. However, this is still a work in progress. Thanks.

[jwnrt]

With #23555 we're now on upstream fusesoc 2.4.3