/bioentity/function/<id> conflict with /bioentity/<type>/<id>

[deepakunni3]

The route /bioentity/function/<id> hides the ability to use /bioentity/<type>/<id> endpoint when type is function.

Also, the response given by the bioentity/function/<id> route is different than /bioentity/<type>/<id> route.

This is because we don't do marshaling of the response in bioentity/function/<id>

[deepakunni3]

This requires,

• refactoring /bioentity/function/<id> such that its returning the proper marshaled association results
• calling /bioentity/function/<id> implementation when type in /bioentity/<type>/<id> is function, to ensure consistency

This is a bigger discussion that involves @lpalbou and @cmungall