[Feature] Private README.md for organization

[changchaishi]

Implemented #29503

Changes:

1. Since individual users and organizations use the same .profile repository name for README.md, adding the private one, I rename the contexts with Public and Private inside them.
2. I wanted to load the private profile the same as GitHub, which uses the view_as query parameter. Still, the existing query scheme is quite limited due to the integration with the search form and the repository paginator, so my workaround is to forcefully bring augmented query strings of member/public to the tmpl file.
3. The drop-down is adopted from the search box's sort by component, we need to discuss the stylings.

Things lack and need further guidance:

1. At the create repository page, the ideal user experience is when the repo name is entered .profile the make repository private checkbox should be disabled and stay unchecked, whereas .profile-private, the checkbox should be disabled and force checked.
2. Follow 1., Tool tips should be added.
3. The translation and CSS for the current drop box and view as public/member feature.

Screenshots
Demo:

Need help:

[changchaishi]

Hi, I listed the behaviors that this PR implemented as below:

• hints to create .profile and .profile-private repos (if users do not follow the hint, profile may not show)
  

• view_as drop down only shows when the user is member in organization and both public and member profiles exist
  

• If there is no profile repo, not showing overview tab
  

• When user is a member of org and logged in, and only 1 profile is present, show that profile
  
  

• When user is not logged in, or not a member, only public profile will show if it is present
  

[wxiaoguang]

Could you add some tests in tests/integration/org_*.go to verify the "view as public" and "view as member" outputs?

If I understand correctly: view as public: private repositories won't be listed.

[changchaishi]

If I understand correctly: view as public: private repositories won't be listed.

In this design view as is only to select profiles. The permission system decides whether the doer can access the README.md. Nothing has changed.

So viewing as public does not mean that a member user will not see private repos listed if he/she already has permission.

[wxiaoguang]

If I understand correctly: view as public: private repositories won't be listed.

In this design view as is only to select profiles. The permission system decides whether the doer can access the README.md. Nothing has changed.

Maybe GitHub also changed their behavior: You are viewing the README and **pinned** repositories as a public user. vs You are viewing the README and repositories as a public user. I wouldn't say it is good but it doesn't block since GitHub does so.

While I still think it needs to add some tests in tests/integration/org_*.go to verify the "view as public" and "view as member" outputs, to cover the new code's behavior.

[changchaishi]

While I still think it needs to add some tests in tests/integration/org_*.go to verify the "view as public" and "view as member" outputs, to cover the new code's behavior.

I'm working on it. Trying to get familiar with the integration tests.

[lunny]

Use tw-hidden class rather than style="display:none".