Follow RFC5785 for /.well-known/ URIs about bp-info-standard

[ellipticasec]

@eosrio any opinion on this. I don’t like to litter the root of my URI path with that. It should be namespaced.

We agree with this new pattern, but since it will require everyone's adoption we would like more opinions on this.

[DenisCarriere]

I'm 👍 adding this pattern, 🤔 however the hard task will be:

• modify EOS voting portals to fetch that URI
• inform all BP's about this new URI pattern

I'd suggest this URI pattern be optional until there's a majority of BP's who are using it.

Easiest way to implement would be to use a symbolic link to support both URI's:

$ ln -s /var/www/html/bp.json /var/www/html/.well-known/eos/aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906/bp.json

@ellipticasec The final URI path would look something like this, correct?

https://bp.eosnation.io/.well-known/eos/aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906/bp.json