feat(lang): Add multiple languages configuration

[hoangnt2]

Refer issue: #25

Some changes

• Add multiple languages configuration (use next-i18next):

  • Apply multiple languages on login page
  • Add language switcher on login page (click on the flags)

  Login page with English language
  

  Login page with Japanese language
  

• Move login page from /auth to /

• Move home page from / to /home

• Remove unnecessary component: PublicContextProvider

• Change Environment variable from SW360_API_URL to NEXT_PUBLIC_SW360_API_URL (can be used on client side)

How to test

Prerequisite

• create .env file at root folder:

   NEXTAUTH_SECRET='secret'
   NEXT_PUBLIC_SW360_API_URL='http://localhost:8080'

• Add 2 lines to /etc/sw360/sw360.properties and create OAuthClient (Access to Admin page and create at least one OAutClient) to use login function:

   rest.apitoken.generator.enable = true
   sw360.liferay.company.id=20099

Procedures

• access http://localhost:3000
• click on the flags

Result

• language will be change

[hoangnt2]

Hi @heliocastro,
The header cannot be added to language files (common.json). Could you ignore them when checking files's license?

[heliocastro]

Yes, you add the exception on the .licencerc.yaml config file. Please add common.json there

[hoangnt2]

Yes, you add the exception on the .licencerc.yaml config file. Please add common.json there

Thanks. But in my opinion, we should keep package-lock.json in our repository. It's recommended.

[heliocastro]

Almost good to go.

@hoangnt2 How complicated is to change the current code to new APP router ?
The ends result will simplify more the code.
Here's the reference
Is likely a future proof update.

If you think is too difficult to do it now, just update the CONTRIBUTORS.md

[hoangnt2]

@heliocastro, I think it's not easy to change to App router now. I will research your reference and try to do it later.

[heliocastro]

Good to go