Edge-home-orchestration-go: [Consideration] Policy for platform support

In general I think we need to support as many H/W platforms as possible in order to popularize our edge-orchestration system (and this will be its distinguishing feature).
But I understand that there may be difficulties in maintaining and testing edge-orchestration on them. Therefore, I suggested making a table on the main page.

The Maintained column indicates which _version_ or _repository tag_ the edge-orchestration was tested latest. Can also add additional information about the build (for example: platform - docker, native, android) and specify a contact person who can help external developers to run edge-orchestration on the this H/W platform.

As I mentioned earlier, it would be good to replace the build.sh script with updated Makefile and configuration file for each H/W or S/W platform. (This will make building the edge-orchestration system more flexible.) Also add descriptions of how to add a new board and configuration to it.

Also, I am ready to test edge-orchestration on Raspberry Pi 3 and HiKey960 boards before release or any request, I can also run edge-orchestration on a Raspberry Pi 4 and add a description for it. Perhaps @t25kim will also provide a description of how to do this on Raspberry Pi 2.

@tdrozdovsky Let us start from this issue report with your potential suggestion (and efforts in terms of PR) of extending platform support.

It's a really good idea to support many platforms, if we could afford to maintain them.

Perhaps @t25kim will also provide a description of how to do this on Raspberry Pi 2.

I've installed the Edge Orchestration with the instruction of RPi3 since the Raspberry Pi OS is the same.

We add new hardware platforms and it is beautiful. But of course, we have concern about the operability and testing on them. I think that we can do the following that to solve this question.
Change the table

| Platform | Maintained |
|-------------------------|------------|
| [x86_64 Linux] | coconut |
| [Raspberry Pi3] | coconut |
| [HiKey960] | coconut |
| [Raspberry Pi3 Cluster] | coconut |
| [Orange Pi3] | coconut |

to this:

| Platform | Maintained | Maintainer | Short comments |
|-------------------------|------------|-------------| ----------------- |
| [x86_64 Linux] | coconut | @lf-edge/edge-home-orchestration-go-maintainers @lf-edge/edge-home-orchestration-go-committers | |
| [Raspberry Pi3] | coconut | @t25kim | |
| [HiKey960] | coconut | @tdrozdovsky | |
| [Raspberry Pi3 Cluster] | coconut | @tdrozdovsky | |
| [Orange Pi3] | coconut | @Vitalii55 | |

and of course indicate the Semantic version on which was tested instead coconut

It's just a draft, let's think about it!

@tdrozdovsky 100% agree!