feat: redefine data source protos

[AnExsomnis]

close vegaprotocol/vega#5714

This PR redefines the proto types related to oracles following the logic presented in vegaprotocol/specs#1161

changes introduced:

• For all external data sources - we care about pubkeys and filters -> so we apply same properties for all (this follows the logic in feat: redefine data sourcing concepts. specs#1161)
  => Everywhere where we have oracle definitions we use the generic data source type instead of custom oracle type

• There is an option where we can embed generic data type into the oracle type - if we really need specific properties for oracles. Same of course can be applied further for different groups of oracles (ETH, or not), bridges as a separate group of external sources, whatever we would need.

The idea behind the changes is:

• use a way as straight forward as possible (doing the correct thing is not always the simplest change)
• do not involve the design with any workaround -> if a workaround is needed - isolate it from the design, so when it needs to be removed - it will not harm the idea.
• have generic types on early stage (like now) ad build up on them if you have to

[jeremyletang]

Not sure I get what these 2 are?

[AnExsomnis]

This is a oneof setting for different type of external spec configuration - we can define an oracle or a bridge.
But this was added in order to show how different external types would be treated anyway, so I'll just leave oracle for now.

[AnExsomnis]

Removed the unused one

[jeremyletang]

Just the commands might need updating relative to these changes.

[AnExsomnis]

Just the commands might need updating relative to these changes.

@jeremyletang , Addressed all of your comments and rebased with develop

[jeremyletang]

Those changes looks good to me @AnExsomnis, let's move them over onto the vega repo on a new PR please. thanks.

[gordsport]

closing as done in:

• feat: fix data source types vega#5980