Request: Add Language drop down on Resources page

## Before creating an issue

- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

- https://about.gitlab.com/resources/

## What does the request INCLUDE?

#### Insert the request here:

* Add a `Language` drop down that will filter the content by language
    * Current languages available: Japanese, Korean, French, Italian, Spanish, Portuguese, Russian, German
* Default the `Language` to English
    * Why: Currently when we enter new assets on the resources page, they appear in the order added. Defaulting to English will show only the English assets, but still allow users to easily select another language.

* Add language field on yml - https://gitlab.com/gitlab-com/www-gitlab-com/-/edit/master/data/resources.yml 

#### Insert here a bulleted list containing links to any relevant resources:

Current languages available: 
* Japanese 
* Korean  
* French   
* Italian    
* Spanish   
* Portuguese     
* Russian
* German

![image](/uploads/51a3a701a6ecc83e84ee6b23c785570f/image.png)


## What does the request EXCLUDE?

#### Insert here any items that are out of scope for this iteration:

*Example: Because we need to get this out quickly, we will not be adding new styles, just updating the content.*

## Why would we do this?



#### Insert here why we want to do this:

We are generating more localized content (eBooks, whitepapers, webcasts, etc), but users do not have an easy way to filter for their preferred language on https://about.gitlab.com/resources/. 

Most of our localized content has not been added to this page, but we would like to add it.

## Who would be involved?

If you are requesting a deliverable from someone, please create a separate issue with a due date, assign it to that individual, and link it to this issue as a blocker.

Please use the R.A.C.I. framework. This includes RESPONSIBLE individuals who are discipline DRIs, a single person ACCOUNTABLE for the project (usually the requestor), a backup for when they accountable is unavailable, the CONSULTED who have knowledge and feedback to consider but not necessarily implement, and stakeholders who should be INFORMED about the project.

#### Insert here a list of people related to the project AND why you listed them.

*Example: @ brandon_lyon as responsible for engineering, @ jhalloran as responsible for UX, @ tbarr for approval, @ dmor as backup for @ tbarr, @ shanerice for analytics and SEO, @ awithers for copy direction, @ lsayers for legal department awareness*.

## When would you like it done?

If your request has multiple delivery dates, please create an epic with a separate issue for each deadline.

Dates without reason are difficult to prioritize. Without enough lead time we will be unable to meet your deadline.

#### Insert here your requested date AND why:

*Example: Our due date is X. We want to launch this page before a press release on X for a trade show that happens on Y. I have submitted this over a quarter in advance with the hope that it can be prioritized as a quarterly OKR.*

- [x] No deadline requested.
- [ ] YYYY-MM-DD-HH, insert reason.

Story points: 2.0