Update allowed expenses for business travel via train

Why is this change being made?

We should allow the same budget for team members to travel via rail as we do for travelling via air. Having a $100 limit for train travel but not having an a similar limit for air travel may disincentivize or outright prevent a team member from using rail as a viable mode of transport for intercity travel, even if the costs/travel time are similar are better than flying.

Given that travel via rail offers many benefits over flying, especially on shorter connections, we shouldn't make this restriction, and instead allow team members make the decision for the mode of transport that works best for them and their own individual circumstances, while staying inside the same budget allowances that would be allowed if they chose to fly.

Some benefits of rail over air

• Train stations are typically located in more convenient centrally located locations and easy to access from both home, and to access at your final destination. This can make the overall travel time shorter via rail over air in many cases, particularly when factoring in the need for security clearance in airports, on top of the need to travel from city-centre to the airport.
• Trains offer more frequent connections and flexibility regarding to departure and arrival times and can often allow travellers switch to an earlier or later service with more ease than an airline will offer.
• They are typically more comfortable, and it's quite possible to work via a 4G/5G hotspot during transit, which isn't an option when flying.
• Trains are also typically more environmentally friendly, and if the option exists, and is cheaper, faster and more convenient for a team member to access, there shouldn't be this additional barrier preventing it as a valid option for travel.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---